|
merchant
|
General
|
All
|
Using multiple product group ID's
|
 WHEN OR WHEN NOT TO USE MULTIPLE PRODUCT GROUPS
Within the conversion script there is an option "productID". This is an ID that is generated by TradeTracker.
It is possible to specify a commission structure per product group.
It is not a description of your product or a category description or something, which is often assumed.
There is only one situation in which multiple product groups (ID's) should be used.
The only reason to use multiple product group ID's is when you offer 2 or more groups of products for which the difference in profit margin is so large that it is a risk to use 1 general commission model. For this purpose and only this, we would advise the usage of an additional product group ID, but even in this situation it is not 100% necessary. You could also base the affiliate commission you want to pay on the average profit margin of your entire shop. Just keep in mind that only a part of your sales will derive from your affiliate marketing endeavours. At the bottom line the actual commission percentages you spent on affiliates (when using your total profit margin to base this on) will always be on the low side in relation to your total average profit-margin percentage.
It is always possible to use product groups. But every situation is client specific.
There is no 1 general product group implementation solution.
The system you use does not matter, the way the system is configured is more important.
In essence using product groups requires just some basic web programming, in principle it is:
if product x is in category A use product group ID 1
else if product x is in category B use product group ID 2
The amount of time a client will need to set up the usage of product groups for their campaign will depend on the individual situation. We can't say that upfront, because we just can't know, because it is always a custom solution. If someone would need 20 different product groups and they/we would have to create very large regular expressions in order to identify each product to be able to set the correct group for it, it will be somewhat time consuming to set up.On the other hand, if the site already uses correct defined categories that are corresponding with the groups they want to use for example, it would be easier to set up. What you need to take in to consideration is how you are able to identify for each product in which product group the product must be. The usage of categories within a site is for example 1 way to do this. In case you do still need to use multiple product groups, there are some things to take into account.
How will you identify the correct product group for each product within an order?
For each product you must be able to identify the correct product group based on a specific identifier, this can be the SKU or category for example.
An order can consist of products from multiple product groups. This implies that the product group will have to be identified on product level, per individual item.
This can be done by a so called basket loop that runs through each product within the order and checks the order category for example.
In the example below a check is done on orderCategory that is a property of order. In case the orderCategory is "hardware" that product gets productID: 321.
$amountsPerProductGroup = array();
foreach ($orders as $order) {
switch($order['orderCategory']) {
case 'hardware':
$productID = '321';
break;
case 'software':
$productID = '322';
break;
default:
$productID = '323'; // "general" product ID.
break;
}
$amountsPerProductGroup[$productID] += $order['orderAmount'];
}
foreach ($amountsPerProductGroup as $productID => $transactionAmount) {
echo <<<TT
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales', // 'sales' or 'lead'.
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '$productID',
transactionID: '[marker]ORDER ID[/marker]',
transactionAmount: '$transactionAmount',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: '',
vc: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&pid=$productID&tid=[marker]ORDER ID[/marker]&tam=$transactionAmount&data=&qty=1&descrMerchant=&descrAffiliate=&event=sales&currency=&vc=" alt="" />
</noscript>
TT;
}
echo <<<TT
<script type="text/javascript">
(function(ttConversionOptions) {
var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null);
var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m';
var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
})(ttConversionOptions);
</script>
TT;
// Leave a blank line here.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=23
|
23-May-2019 15:07:36 |
|
merchant
|
General
|
All
|
Web shop systems overview
|
SETTING UP THE REDIRECT INSTRUCTIONS | OUR UNIVERSAL CONVERSION SCRIPTS | IMPLEMENTATION CONSIDERATIONS
After selecting your shop, you are able to use the filters to select the correct version of your shop (if available) by making a selection from the Version dropdown menu.
You are able to use the filters in general to navigate through the available content on this portal.
The list below are the most popular solutions that are used, but your solution might also be part of the portal even though it might not be listed below.
Please check the Implementation dropdown menu, to see if your shop is listed.
MOST POPULAR SHOPS SYSTEM SOLUTIONS:
DISCLAIMER
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
SETTING UP THE REDIRECT INSTRUCTIONS
OUR UNIVERSAL CONVERSION SCRIPTS
IMPLEMENTATION CONSIDERATIONS
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=3
|
14-Jan-2015 11:42:02 |
|
merchant
|
VirtueMart (Joomla)
|
2.0.0 and higher
|
Standard implementation
|
 VIRTUEMART 2.0.0 AND HIGHER (JOOMLA) TRADETRACKER CONVERSION IMPLEMENTATION
Seeing as Virtuemart (Joomla) uses php you can download the redirect file here download index.php please add your domainName to line 6 like after downloading the index redirect file, like:
$domainName = 'yourdomainWithoutWWW.com';
After adding your domain to the index file, it should be uploaded to a folder in the root of your website. The folder must be named a word that best represents your webshop's content.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines.
VIRTUEMART CONVERSION IMPLEMENTATION
We have created a general TradeTracker conversion handler file for Virtuemart 2.0.0 and higher (Joomla) that also must be placed on your server.
Download: tradetracker.php No modifications must be made to this file.
Upload tradetracker.php to your server in folder /components/com_virtuemart/views/cart/tmpl/
After that open and edit the order_done.php file (also located in /components/com_virtuemart/views/cart/tmpl/ )
Within the order_done.php file locate the following line of code:
[marker]echo $this->html;[/marker]
Below that line copy and paste the following code:
$tt_campaignID = '[marker]CAMPAIGN_ID[/marker]';
$tt_productID = '[marker]PRODUCT_ID[/marker]';
$tt_trackingGroupID = '[marker][/marker]';
$tt_scriptTag = include_once 'tradetracker.php';
echo $tt_scriptTag;
After these steps are executed, the campaign is ready to be tested.
Make sure you use the TradeTracker Tracking Test URL before doing the test. If you don’t have the test URL, please ask your account manager to provide it to you.
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=28
|
12-Dec-2014 14:28:51 |
|
merchant
|
xt:Commerce
|
3
|
Overview
|
 XT:COMMERCE 3 TRADETRACKER CONVERSION IMPLEMENTATION
SETTING UP THE REDIRECT
Seeing as XT:Commerce uses php you can download the redirect file here download index.php After downloading, please add your domainName to line 6.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines. When the redirect is working, follow the instruction for setting up the conversion registration below.
We have created a general TradeTracker conversion handler file for xt:Commerce 3 that must be placed on your server. No modifications must be made to this file.
Download the tradetracker.php file for xt:Commerce here
Log in to your FTP account and upload the tradetracker.php file to the /includes/ folder of your xt:Commerce installment.
Open and edit the file checkout_success.php that is located in the root of your XT:Commerce installation. Within checkout_success.php locate the following line of code:
$main_content = $smarty->fetch(CURRENT_TEMPLATE.'/module/checkout_success.html');
ABOVE this line place the following code:
// Begin Tradetracker xt:Commerce code
$tt_campaignID = '[marker]CAMPAIGN_ID[/marker]';
$tt_productID = '[marker]PRODUCT_ID[/marker]';
$tt_imageTag = include './includes/tradetracker.php';
$smarty->assign('tt_imageTag', $tt_imageTag);
// End TradeTracker xt:Commerce code
Save and/or upload the file to your server.
Locate your checkout_success.html template file. This file is part of the theme your are using. and normally would be found at the following location:
/templates/{TEMPLATE_NAME}/module/checkout_success.html
Open and edit the file checkout_success.html and at the bottom of this file add the following code:
<!-- TradeTracker conversion tracking start -->
{$tt_imageTag}
<!-- TradeTracker conversion tracking end -->
Save and/or upload the file to your server.
If your redirect is working the implementation can be tested.
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=14
|
28-Jan-2016 14:51:14 |
|
merchant
|
xt:Commerce
|
4
|
Standard implementation
|
XT:COMMERCE 4 VEYTON TRADETRACKER CONVERSION IMPLEMENTATION
SETTING UP THE REDIRECT
Seeing as XT:Commerce uses php you can download the redirect file here download index.php After downloading, please add your domainName to line 6.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines. When the redirect is working, follow the instruction for setting up the conversion registration below.
Log in to your FTP account and open and edit the file xtCore/pages/page_action/checkout.success.php
At the bottom of the file you will find a php closing tag ( ?> ) above this closing tag the code that is found here must be added:
// TradeTracker conversion script
$campaignID = '[marker]CAMPAIGN_ID[/marker]';
$productID = '[marker]PRODUCT_ID[/marker]';
$orderID = !empty($success_order->oID) ? htmlspecialchars($success_order->oID) : '';
$orderAmount = empty($success_order->order_total['total']['plain']) ? 0.00 : (float) $success_order->order_total['total']['plain'] / 1.2; // The 1.2 is your VAT ratio.
$trackingCode = "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '$campaignID',
productID: '$productID',
transactionID: '$orderID',
transactionAmount: '$orderAmount',
quantity: '1',
descrMerchant: '$descrMerchant',
descrAffiliate: '',
currency: '',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?cid=$campaignID&pid=$productID&tid=$orderID&tam=$orderAmount&qty=1&event=sales\" alt=\"\" />
</noscript>
<script type=\"text/javascript\">
(function(ttConversionOptions) {
var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null);
var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m';
var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
})(ttConversionOptions);
</script>";
define('TRADETRACKER_TRACKING_CODE', $trackingCode);
Save and/or upload the file to your server.
Navigate to: /templates/YOUR_THEME_SKIN_DIRECTORY/xtCore/pages/checkout/subpage_success.html
Open and edit the file subpage_success.html and at the top of this file add
{txt key=TRADETRACKER_TRACKING_CODE}
Save and/or upload the file to your server.
If your redirect is working the implementation can be tested.
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=39
|
14-Mar-2019 15:52:04 |
|
merchant
|
Magento
|
Plugin
|
1.x - 2.x
|
 MAGENTO CONVERSION IMPLEMENTATION
In order to get tracking up and running swiftly within your Magento webshop, we gladly point you to the available plugins.
Provided below are plugins for Magento version 1.7.2 - 1.9.X, as well as a plugin for Magento versions 2.3 - 2.X.
Magento version 2
Magento version 1 by third party Magmodules.eu.
For support, please refer to Magmodules in case you might run into configuration issues. Their professional support has short response times.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=70
|
15-Dec-2021 16:39:24 |
