|
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 |
|
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
|
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
|
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
|
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
|
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
|
Server to Server (S2S) tracking
|
Setting up Server to Server (S2S) tracking
Server to server tracking is used in situations where regular conversion registration is not possible by means of placing our tracking code within the publicly available pages on your website (known as "client-side tracking"). The S2S method relies on a unique click identifier to be stored on your server and passed back at the time of the conversion.
We are able to pass our unique click identifier to each page on your website and you are free to choose exactly what the name of this parameter should be, e.g. "someparameter".
The tracking data value is a unique reference to identify clicks within our system and is unique for each incoming click on your website.
As a result, a link to one of your landing pages will look something like:
http://yourwebsite.com/landing/page?someparameter=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker]
Please note we always send this parameter url-encoded. Also, it's important this value is stored somewhere within a storage of choice, e.g. a memory database and/or a relational database, depending on the usage. When using a database, it can for example be stored within a column ttClickID or any other column name you prefer.
How to pass back the click identifier
Whenever a conversion is triggered for which an affiliate should receive a reward, this click identifier should be passed back to TradeTracker.
One of the tasks that lies ahead for your development team, is to store this unique click identifier, together with the information that is used to trigger this conversion.
Example
Let's assume you run an online gaming website and you reward affiliates for bringing in new players. It's important that our unique click identifier is stored together with the new player information so that it can be accessed at the time of conversion trigger.
Within a database it would look something like:
| id | name | user | eml | regdate | ttClickID |
| 111 | J. Smith | jsmith00 | jsmith@eml.net | 2014-09-01 | [marker]0::12345::abc::::1405418672[/marker] |
| 112 | J. Doe | player123 | doe.j@email.org | 2014-09-02 | 12::54321::def::::1405419867 |
LEAD CONVERSION CALLBACK
In case an event is triggered that resembles a lead conversion (e.g. user registration), the following callback format is used:
https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&data=[marker]{ttClickID}[/marker]&vc={voucherCode}
SALES CONVERSION CALLBACK
If an event is triggered that resembles a sales conversion (purchase, booking), the following callback format is used:
https://ts.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&tam={transactionAmount}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}¤cy={currency}&data=[marker]{ttClickID}[/marker]&vc={voucherCode}
In the above callbacks the {ttClickID} is tied to a fixed "data" parameter and its value must be replaced by the value saved during the initial click (and eventually stored within a database, like the table above).
Note: Please make sure all values are URL-encoded.
Example formatted callback
https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid=123456&descrMerchant=new%20player&descrAffiliate=new%20player&data=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker]
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=31
|
30-Nov-2021 17:07:39 |
|
merchant
|
General
|
All
|
Multi country campaign conversion script
|
MULTI COUNTRY CAMPAIGN CONVERSION SCRIPTS
TradeTracker campaigns get a unique campaign ID per country in which the campaign will be active. The Tracking Group ID is used to be able to use just 1 general conversion script on your confirmation page, instead of a script for each country in which the campaign is active. The way that this works is that our system will check for each campaign within the tracking group where the originating click came from and assigns any resulting conversions to the correct campaign in the correct country.
The multi-country conversion script should only be used after receiving a Tracking Group ID from your account manager.
Please note that the script you choose below must contain 1 of your campaign ID's (in general just the main campaign ID) in order for the conversion scripts to work.
The campaign ID that is added is only used to check if the main campaign is active, the tracking group number is used to assign the conversion to the correct campaign in our system.
MULTI COUNTRY CAMPAIGN SALES CONVERSION SCRIPT
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[marker]ORDER_ID[/marker]',
transactionAmount: '[marker]ORDER_AMOUNT[/marker]',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: '',
vc:'',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&tam=[marker]ORDER_AMOUNT[/marker]&data=&qty=1&descrMerchant=&descrAffiliate=&event=sales&currency=[marker]EUR[/marker]&vc=" alt="" />
</noscript>
<script type="text/javascript">
// No editing needed below this line.
(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>
MULTI COUNTRY CAMPAIGN LEADS CONVERSION SCRIPT
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'lead',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[marker]ORDER_ID[/marker]',
descrMerchant: '',
descrAffiliate: '',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src="//tl.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&data=&descrMerchant=&descrAffiliate=&event=lead" alt="" />
</noscript>
<script type="text/javascript">
// No editing needed below this line.
(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>
OUR UNIVERSAL CONVERSION SCRIPTS
PRE-CONFIGURED WEB SHOP CONVERSION IMPLEMENTATION SOLUTIONS
SETTING UP THE REDIRECT INSTRUCTIONS
IMPLEMENTATION CONSIDERATIONS
VARIABLES OVERVIEW AND DESCRIPTIONS
| Available variables | Possible value(s) | Example | Required | Description |
| type | sales or lead | sales | Yes | Define if the conversion is a sale or a lead. |
| campaignID | Numeric string | 1234 | Yes | Your campaign ID.The campaign ID as provided by TradeTracker. |
| productID | Numeric string | 4321 | Yes | Your product ID. The product ID as provided by TradeTracker. |
| transactionID | Textual string | ABC-12345 | Yes | Your shop's internal and unique order identifier. The transaction identifier (e.g. orderID) is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. |
| transactionAmount | Numeric string | 123.45 | Yes, if type is 'sales'. | Transaction amount variable. The transaction amount is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. In case of a lead campaign this can be left blank or set to '0'. |
| quantity | Numeric string | 1 | No | Intended for statistical analysis in future software releases. You are able to specify the quantity of the order here. Currently this does not affect the registration of the order, in the future this will be used to be able to calculate the order amount for example (if this has added value for you) and it will be used for statistical information. |
| descrMerchant | Textual string | Samsung UE55HU7500 | Yes | Detailed description of the order. Used for statistical purposes. Visible for the merchant only. You can add variable values here and/or other order information you might want to see in your TradeTracker account. Use this to add product information or order information. |
| descrAffiliate | Textual string | Samsung Ultra HD TV | Yes | Description of the order. Visible for affiliates only. Used by affiliates for campaign optimisation. |
| currency | Textual string | USD | No | Currency of the transaction. ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Defaults to company currency if left empty. Also used in combination with our automatic currency conversion option This option is turned off by default. Ask your account manager if you need this option to be activated. |
| trackingGroupID | Numeric string | 11 | Leave blank by default unless instructed to do otherwise by TradeTracker | Used to group campaigns for multiple countries. |
| vc | Textual string | Welcome-123 | No | The (main) discount code used for the order in question. Used in case you would like to work with unique voucher codes for certain publishers |
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=29
|
08-Dec-2020 10:50:12 |
|
merchant
|
General
|
All
|
Redirect
|
IMPLEMENTING TRADETRACKER REDIRECT AND CONVERSION INSTRUCTIONS AND CONSIDERATIONS
The articles on these pages are created to help you implement our tracking and conversion registration method.
If you arrived at this portal by using a link that was sent to you, we would like to inform you about the accompanying document to these pages.
This document contains more or less similar information as to be found on this site, but is structured chronological and contains links to the relevant pages on this site, making it somewhat easier to read, depending on what you prefer.
The document is part of the start mail you received or available in your account.
Implementing our click registration and conversion tracking should take about 30 minutes up to 2 hours for general situations.
Although it can be done in 15 minutes in case you are already familiar with setting it up using an available pre-configured implementation method and if there are no unexpected surprises. It can however be longer in more complex set-ups with more stakeholders or when encountering other problems.
We highly recommend you to read the information in the document or on this site.
These articles contain important information about how, why and what you should do in order to set up your campaign successfully.
Setting up the TradeTracker tracking consists of 2 parts:
1) Registering a click from the affiliate’s website to your site.
2) Registering resulting conversions to be able to match the click to the sale.
In order to be able to implement our tracking system, you must be able to:
1) Create a redirect location on your (sub) domain.
2) Make modifications to the checkout success / order confirmation page of your web shop system.
The first thing that needs to be done is getting the click registration mechanism to work.
The redirect is based on creating a location on your domain which will handle all incoming clicks from your affiliates. This can be done by either creating a separate rewrite path or physical directory and making one of our redirect example code files available to handle the incoming clicks. Optionally, you may also create a subdomain (e.g. offers.merchant.com) and making the desired redirect available within the root of your subdomain. This is the preferable method in case you want to keep this implementation separate from your regular developments on your main domain.
The available languages we offer are ASP (.asp) | Coldfusion (.cfm) | CSHARP (.aspx) | JSP (.jsp) | PERL (.pl) | PHP (.php) | Python (.py) | Visual Basic ASPX (.aspx).
DOWNLOAD THE AVAILABLE REDIRECT REDIRECT SCRIPT EXAMPLES HERE and extract the zip-file to your computer.
The zipped file contains directorys that represent the programming language of the redirect script example. You should choose an redirect script example in a language (extension) that is supported by your server.
ADD YOUR DOMAIN NAME TO THE INDEX REDIRECT FILE
The redirect script example to use depends on the type of server and the programming language that is supported by your server.
To make sure our tracking is working as intended, the domain of your website (without www. ) must be added to the redirect file. Check the file for the "domainName" variable and change to your main domain accordingly.
If your shop is running on www.merchant.com or shop.merchant.com for example, the domainName value to enter would be "merchant.com".
By default the redirect script example we provide should work in most situations. They are created, tested and verified to work for the majority of our clients. We do not encourage further modification of the provided redirect script example, unless you have a very good reason to do so and know exactly what you are doing.
MAKING THE REDIRECT AVAILABLE
Within the introduction e-mail that you received from your account manager a suggestion for the location of the redirect location is made. If you decide to use an other location, please communicate this to your account manager because the correct location is needed to get your campaign to work as intended.
CHOOSING A LOCATION FOR THE REDIRECT
The redirect location name should be a phrase that best represents your shop or topic of your site. If you have a website that sells fashion items or clothing, the name of the redirect directory should represent this. For instance in this case it might be www.yourwebsite.com/fashion/ or www.yourwebsite.com/clothing/.
Please refrain from using a name that resembles any connection or relation to TradeTracker like www.yourwebsite.com/tt/ www.yourwebsite.com/tracking/ www.yourwebsite.com/tradetracker/ or www.yourwebsite.com/redirect/ for example.
You should verify that the suggested directory is not already part of your website’s link structure. This can be the case if URL rewriting is used for the suggested directory and content is already attached to the suggested location. If that is the case, please think of an alternative location/directory to place the redirect file.
Turn URL rewriting off in case you use an actual "physical" directory
In case your site is using URL rewriting to create pretty links on your website, URL rewriting must be turned off for the redirect directory in order for it to work correctly. This is done in different ways for different server environments. On an Apache web server, the URL rewrite engine can be turned off for a specific directory by placing an .htaccess file within the redirect directory containing the line:
RewriteEngine Off
For more information about URL rewriting and links to different server settings we refer you to Wikipedia - URL Rewrite Engine.
In case your server supports .htaccess files you can download a zipped .htaccess file to use here.
SUMMARY TO SET UP THE REDIRECT LOCATION
1. Determine the server environment and choose the programming language format accordingly (or create one based on one of the example codes)
2. Create the redirect location (either a rewrite, physical directory or subdomain)
3. Set the domainName variable with your main domain (without www.) in the redirect script example
4. Make the redirect script publicly available at the chosen location and if using an actual physical directory, turn off the URL rewrite engine according to your server configuration options
5. Use the tracking test URL that corresponds to the redirect location to test the redirect
When these steps are done, you are ready to test the redirect to your site by using the tracking test link.
If you did not receive the tracking test link or used a different then suggested redirect location, please contact your account manager.
SETTING UP THE TRADETRACKER CONVERSION SCRIPT AND IMPLEMENTATION CONSIDERATIONS
Before you start copying and pasting the codes that can be found by clicking the links below to your site and come to the conclusion that it's not working as you had planned, please hold on to your horses. Implementing our conversion script requires some thought and consideration. The reason for this is that there are a lot of options and configuration situations to take into account.
Do you have a custom built website? If so, what program language is used? Do you use a Payment Service Provider? An existing web shop system? Are for example things that influence the technical implementation strategy to follow.
We have described a couple of things for you to consider or determine before continuing the implementation.
When you have a clear picture of your technical environment and the other factors described above, you have to main options:
PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS
click the link above to see if we have a solution for your environment available.
The advantages are that these solutions are already configured to use the correct variable values and tested in a default installation of the web shop system.
OUR UNIVERSAL CONVERSION SCRIPTS.
Our universal script is the script that we use to create the web shop specific solutions.
The script requires the variable values that are needed to register conversions within our system to be added manually, but it can be used for any situation.
It does require some basic programming knowledge of the environment in which the script must be placed or use the supported variable placeholders of your shop or environment.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=1
|
30-Jul-2020 14:01:11 |
|
merchant
|
General
|
All
|
General conversion script
|
GENERAL TRADETRACKER CONVERSION SCRIPTS Click here in case you need to use a MULTI COUNTRY SOLUTION with a TRACKING GROUP ID
Here you will find our general conversion scripts that can be used to place on the order confirmation page or thank you page of your site.
To register conversions, the script must be populated with information from your site.
SALES CONVERSION SCRIPT EXAMPLE
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[marker]ORDER_ID[/marker]',
transactionAmount: '[marker]ORDER_AMOUNT[/marker]',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
vc: '',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&tam=[marker]ORDER_AMOUNT[/marker]&data=&qty=1&descrMerchant=&descrAffiliate=&event=sales&currency=[marker]EUR[/marker]&vc=" alt="" />
</noscript>
<script type="text/javascript">
// No editing needed below this line.
(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>
LEAD CONVERSION SCRIPT EXAMPLE
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'lead',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[marker]{transactionID}[/marker]',
descrMerchant: '[marker][/marker]',
descrAffiliate: '[marker][/marker]'
});
</script>
<noscript>
<img src="//tl.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]{transactionID}[/marker]&data=[marker][/marker]&descrMerchant=&descrAffiliate=&event=lead" alt="" />
</noscript>
<script type="text/javascript">
// No editing needed below this line.
(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>
VARIABLES OVERVIEW AND DESCRIPTIONS
| Available vars | Value(s) | Example | Required | Info |
| type | sales or lead | sales | Yes | Define if the conversion is a sale or a lead. |
| campaignID | Numeric string | 1234 | Yes | Your campaign ID.The campaign ID as provided by TradeTracker. |
| productID | Numeric string | 4321 | Yes | Your product ID. The product ID as provided by TradeTracker. |
| transactionID | Textual string | ABC-12345 | Yes | Your shop's internal and unique order identifier. The transaction identifier (e.g. orderID) is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. |
| transactionAmount | Numeric string | 123.45 | Yes, if type is 'sales'. | Transaction amount variable. The transaction amount is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. In case of a lead campaign this can be left blank or set to '0'. |
| quantity | Numeric string | 1 | No | Intended for statistical analysis in future software releases. You are able to specify the quantity of the order here. Currently this does not affect the registration of the order, in the future this will be used to be able to calculate the order amount for example (if this has added value for you) and it will be used for statistical information. |
| descrMerchant | Textual string | Samsung UE55HU7500 | Yes | Detailed description of the order. Used for statistical purposes. Visible for the merchant only. You can add variable values here and/or other order information you might want to see in your TradeTracker account. Use this to add product information or order information. |
| descrAffiliate | Textual string | Samsung Ultra HD TV | Yes | Description of the order. Visible for affiliates only. Used by affiliates for campaign optimisation. |
| currency | Textual string | USD | No | Currency of the transaction. ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Defaults to company currency if left empty. Also used in combination with our automatic currency conversion option This option is turned off by default. Ask your account manager if you need this option to be activated. |
| vc | Textual string | DISCOUNT50 | No | Voucher code variable. The voucher code is a variable value that is used on checkout page of your web shop. |
SETTING UP THE REDIRECT INSTRUCTIONS
IMPLEMENTATION CONSIDERATIONS
PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=27
|
07-Jun-2019 15:28:45 |
