Target group Name Version Version info Implementation steps Last modified
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. The :: are part of the tracking data value and are used as column separators in order to allow us to identify the correct values within the tracking data value.
The actual structure that makes up the complete tracking data value is: materialID::affiliateID::reference::checkSum::time

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]
This value must be stored in your database. For example in a column ttClickID or any other column 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 TradeTracker click identifier within a database, 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:

idnameuseremlregdatettClickID
111J. Smithjsmith00jsmith@eml.net2014-09-01[marker]0::12345::abc::::1405418672[/marker]
112J. Doeplayer123doe.j@email.org2014-09-0212::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/?cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&data=[marker]{ttClickID}&vc={voucherCode}[/marker]

SALES CONVERSION CALLBACK
If an event is triggered that resembles a sales conversion, the following callback format is used:

https://ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&tam={transactionAmount}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&currency={currency}&data=[marker]{ttClickID}&vc={voucherCode}[/marker]
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/?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]



SERVER 2 SERVER EXPLAINED IN MORE DETAIL

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=31
19-Apr-2019 12:03:55
merchant General All Conversion GENERAL TRADETRACKER CONVERSION IMPLEMENTATION CONSIDERATIONS.

SETTING UP THE REDIRECT INSTRUCTIONS
PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS
OUR UNIVERSAL CONVERSION SCRIPTS

Do you use a Payment Service Provider to handle your transactions?
Using a Payment Service Provider (PSP) can be a convenient option to handle the transactions that are done via your web shop. Please be aware that using a PSP in most cases requires additional work to set up our conversion registration mechanism correctly. A problem that often occurs is that our implementation instructions are executed correctly, but when testing the campaign no transaction information is passed back to the actual order confirmation page on your website (where our conversion script is located). This results in an unsuccessful test, because the information we need to pass back to our system is not available within the script placed on the checkout success page. The general solution to this is to configure your PSP process in such a way that the PSP passes back the transaction information to the order success page on your website. This can be done from within the PSP administrative interface in most cases.

In case you encounter issues implementing our conversion script when using a PSP, we advise you to provide this document to the PSP and ask them how it would be possible to get our conversion mechanism to work with their system. They should be able to provide a solution for this. A workaround would be to add our conversion script one step before the visitor is redirected to the PSP’s environment in which the actual payment is done. All orders that are registered in our system will always have to be assessed either way, so it might be an option to use this solution. This would save valuable time in setting up your campaign, but would result in a slightly higher conversion rejection rate for your affiliates.

Will your campaign start in one or multiple TradeTracker countries?
In case you are about to start a campaign in multiple TradeTracker countries, it’s important to inform your account manager about this. Starting a campaign in multiple territories will partly determine the implementation strategy to follow. In case you have agreed to run your campaign in multiple countries it is important to know how the checkout process on your site is configured. Seeing as your campaigns are registered on country level by default, every campaign will have an individual campaign ID per country and the correct ID must be used for each transaction. Basically it can be either of the options described below.

Option / example 1
You have separate website instances for each country or a general website with separate checkout pages on which you can place the conversion script per country (preferred solution). If your site uses multiple instances (or checkout pages) that are corresponding to the countries in which the campaign will run, it is possible to add the corresponding scripts (with the correct campaign ID per country) to each separate instance of the order confirmation page.

Option / example 2
You have one general website for all different countries and you use one general checkout process. If you are unable to differentiate between countries on your website, it is possible to use a multi-country script solution. The way this works is that a tracking group is created to combine the campaign ID's of your country specific campaigns. Our system will perform a background system check between all campaigns and tries to identify the originating click in order to match the conversion to the correct campaign. In case we are unable to make a correct match, a fall-back method is used to account the conversion to all country campaigns for which a click is found. In order to account the conversion to the correct campaign manual intervention is needed. General practice is to account the sale to the last originating click. Using a tracking group ID might cause some overhead in assessing conversions making this the lesser preferred way to go. The tracking group solution should only be used in case you are unable to use a variable campaign ID within our conversion script based on the visitor’s country or site entry point.

Sales or lead conversion?
The sales conversion script is intended for registering actual sales transactions. In order to do this, the script needs to contain more information about the transaction in comparison to the information that is needed to register a lead. A sales conversion event contains actual order value information and a connection to your administration, such as an internal order identifier. In case of a lead conversion (an information request or brochure download for example) no order and order value specific information is needed. A lead conversion will have a pre-set fixed commission within our system. The unique lead identifier can for example be the ID of the prospect. Sales and leads are registered separately within our system for easy analysis.

Pre-configured web shop specific implementation instructions
We have created dedicated pages for the specific web shop implementation solutions available. At the bottom of the page about setting up the conversion and general set-up considerations or by navigating through the implementation system when using the "Visit the TradeTracker implementation portal" link, you can select the web shop system you are using and follow the instructions accordingly. In case you encounter or experience issues when implementing our tracking by using our implementation instructions, please report this to your account manager and describe (in detail) the steps you took and provide the codes and/or files you used for your implementation to your account manager. 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 implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of (conflicting) plug-ins into account. Besides that there are a lot of other factors that can have impact on the correct workings of our tracking and conversion registration system. It is impossible to provide all possible solutions for problems that might even not exist already.

My shop system is not listed in the portal, what to do?
In case your specific shop is not listed in the examples, you may provide this document to the supplier of your web shop system or your webmaster and ask about the possibilities to implement our tracking within the system you are using.
If they provide a solution or implementation instructions to implement our tracking according to our specifications, it would be highly appreciated if the information about your shop, the version you are using and the actual solution or implementation instructions you received would be shared with your account manager. This information would then be assessed carefully in order to determine whether it can be shared on the portal for others to use.

TRADETRACKER GENERAL CONVERSION SCRIPTS

When you have a clear picture of your technical environment and the other factors described above, you have two main options:

Look at the PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS 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.

Use OUR UNIVERSAL CONVERSION SCRIPTS. This solution requires the variable values that are needed to register in our system to be added manually, but can be used for any situation. It does require some basic programming knowledge of the environment in which the script must be placed in order to do this correctly.

VARIABLES OVERVIEW AND DESCRIPTIONS

Available variablesPossible value(s)ExampleRequiredDescription
typesales or leadsalesYesDefine if the conversion is a sale or a lead.
campaignIDNumeric string1234YesYour campaign ID.The campaign ID as provided by TradeTracker.
productIDNumeric string4321YesYour product ID. The product ID as provided by TradeTracker.
transactionIDTextual stringABC-12345YesYour 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.
transactionAmountNumeric string123.45Yes, 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'.
quantityNumeric string1NoIntended 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.
descrMerchantTextual stringSamsung UE55HU7500YesDetailed 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.
descrAffiliateTextual stringSamsung Ultra HD TVYesDescription of the order. Visible for affiliates only. Used by affiliates for campaign optimisation.
currencyTextual stringUSDNoCurrency 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.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=2
14-Mar-2019 14:56:18
merchant Strato Webshop All Single Country Campaign with campaign and order ID STRATO WEBSHOP TRADETRACKER SINGLE CAMPAIGN / COUNTRY CONVERSION IMPLEMENTATION

You can use the filter options above to select your shop system, the version of your shop. The Version info selection is a short description of the implementation method we created for the shop you selected.

GERMAN
Navigate to (or click the link and login): Einstellungen --> Warenkorbeinstellungen --> Texte

ENGLISH
Navigate to (or click the image or link and login): Settings --> Basket Settings --> Texts

Or just click this image:


Scroll down to: Texts in both order processes

Look for the entry: Text for confirmation page / Affiliate tracking code

In German, scroll down to: Texte in beiden Bestellprozessen

Look for the entry: Text für Bestätigungsseite / Affiliate-Tracking-Code



Click the < > html button. (Click in the text input field and click the < > html button).

It's advisable to add the script below for both language entries, seeing as a user can specify the language. Add the following codes to both entry fields.

NOTE: Make sure to click the < > html button first!

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '#OrderNumber',
transactionAmount: '#OrderTotalAmountGross', // Format: 123.45
quantity: '1',
descrMerchant: '#CustomerNumber', // Detailed description of the order
descrAffiliate: '', // Description of the order.
currency: '#CurrencyCode' // Use the ISO 4217 standard, e.g. USD, EUR, GBP, SEK, DKK, NOK, HUF, PLN.
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=#OrderNumber&tam=#OrderTotalAmountGross&data=&qty=1&descrMerchant=#CustomerNumber&descrAffiliate=&event=sales&currency=#CurrencyCode" 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>


Click the SAVE button to save these settings.

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]=21
14-Mar-2019 14:53:44
merchant Oxid eShop 4 Overview OXID eSales Shop v4.x TRADETRACKER CONVERSION IMPLEMENTATION

You can use the filter options above to select your shop system, the version of your shop.
The Version info selection is a short description of the implementation method we created for the shop you selected.

After setting up the redirect for your campaign, like discussed in SETTING UP THE REDIRECT.

ADD THE TRADETRACKER CONVERSION SCRIPT TO THE THANKYOU.TPL FILE OF YOUR THEME
Our conversion trackingcode must be added to the thankyou.tpl file that is part of the actual theme you are using for your shop.

To identify the theme your are using, login to the administration section of your shop and go to: Home --> Extensions --> Themes

The theme you are using is indicated by a green square in the Active column. After identifying the theme:

navigate to the thankyou.tpl file in the following path on your FTP:

/application/views/YOURTHEME/tpl/page/checkout/thankyou.tpl

Download, open and edit the file or open and edit the file from your FTP directly, whatever you prefer.

Locate {assign var="basket" value=$oView->getBasket()} in the thankyou.tpl file.

Place the following script directly below that:

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[{ $order->oxorder__oxordernr->value }]',
transactionAmount: '[{ $order->getTotalOrderSum() }]',
quantity: '1',
descrMerchant: '[{ $oxcmp_user->oxuser__oxcustnr->value }]',
descrAffiliate: '',
currency: '[{ $order->oxorder__oxcurrency->value }]'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[{$order->oxorder__oxordernr->value }]&amp;tam=[{ $order->getTotalOrderSum() }]&amp;data=&amp;qty=1&amp;descrMerchant=[{ $oxcmp_user->oxuser__oxcustnr->value }]&amp;descrAffiliate=&amp;event=sales&amp;currency=[{ $order->oxorder__oxcurrency->value }]" 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>

If your campaign ID and product ID provided by TradeTracker is not already part of the example above it should be added manually.

After placing the conversion script, save the file to you FTP and the configuration can be tested by using the tracking test url and placing an order in your shop after clicking the test link.

Finished! Ready for testing
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=6
14-Mar-2019 14:52:28
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&amp;pid=$productID&amp;tid=$orderID&amp;tam=$orderAmount&amp;qty=1&amp;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 14:52:04
merchant Strato Webshop All Multi country solution with tracking group ID STRATO WEBSHOP TRADETRACKER CONVERSION IMPLEMENTATION

GERMAN
Navigate to Einstellungen --> Warenkorbeinstellungen --> Texte

ENGLISH
Navigate to Settings --> Basket Settings --> Texts



Scroll down to: Texts in both order processes

Look for the entry: Text for confirmation page / Affiliate tracking code

or for German, scroll down to: Texte in beiden Bestellprozessen

Look for the entry: Text für Bestätigungsseite / Affiliate-Tracking-Code



Click the < > html button. (Click in the text input field and click the < > html button).

It's advisable to add the script below for both language entries, seeing as a user can specify the language. Add the following codes to both entry fields.

NOTE: Make sure to click the < > html button first!

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
trackingGroupID: '[marker][/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '#OrderNumber',
transactionAmount: '#OrderTotalAmountGross',
quantity: '1',
descrMerchant: '#CustomerNumber',
descrAffiliate: '',
currency: '#CurrencyCode'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=#OrderNumber&tam=#OrderTotalAmountGross&data=&qty=1&descrMerchant=#CustomerNumber&descrAffiliate=&event=sales&currency=#CurrencyCode" 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>

This will result in something like:



Click the SAVE button to save these settings.

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]=22
14-Mar-2019 14:51:40
merchant Weebly Webshop NA Standard implementation WEEBLY WEBSHOP TRADETRACKER CONVERSION IMPLEMENTATION

The code below must use your campaign ID and product ID that you received from us.

The code must be pasted as custom tracking code by navigating to:

STORE >> ADVANCED >> Add custom tracking code and add it to the Receipt page input field and Save it

COPY THIS CODE (if needed replace CAMPAIGN_ID and PRODUCT_ID with your own ID's)

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '{txid}',
transactionAmount: {total} - {tax} - {shipping},
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid={txid}&amp;tam={total}&amp;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>


STEP-BY-STEP GUIDE
Login to your Weebly account and click edit for the site you want to add our conversion script.

Navigate to STORE >> ADVANCED >> Add custom tracking code:



Paste our conversion code to the Receipt page input field:



Click Update Changes.

The implementation can be tested.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=37
14-Mar-2019 14:51:22
merchant Shopware 4 Standard implementation SHOPWARE 4 CONVERSION IMPLEMENTATION

You can use the filter options above to select your shop system, the version of your shop. The Version info selection is a short description of the implementation method we created for the shop you selected.

SETTING UP THE REDIRECT
Seeing as Shopware uses php you can download the redirect file here download index.php. After downloading, 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 web shop's content.
For more information regarding setting up the redirect we refer you to SETTING UP THE REDIRECT GUIDELINES.

SETTING UP THE CONVERSION
STEP 1 The conversion script below should be added to the finish.tpl file that is part of the front-end template you are using and should be located in the folder /templates/_yourtheme_local/frontend/checkout/finish.tpl

Please note: If you for example are using the theme emotion in pink. The colour variation of the theme is in the /emotion_pink/ folder. This folder contains only colour information.
The finish.tpl file should be added to the folder _emotion_local so the theme name starting with an underscore.

For you convenience you can download finish.tpl (from version 4.2.3) here and save it to your computer and upload it to the folder or download finish.tpl from the base template from your server and upload that to the _local folder of the theme you are using.

If you not sure what to do or how this works, please read the sections ABOUT THE SHOPWARE TEMPLATE STRUCTURE and HOW TO IDENTIFY THE USED TEMPLATE/THEME FOR YOUR SHOPWARE SYSTEM AND ADDING THE FINISH.TPL at the bottom of this article.

STEP 2 Open finish.tpl and add the following conversion code above [marker]{/block}[/marker] (the block piece of code is at the bottom of the finish.tpl file):

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '{$sOrderNumber}',
transactionAmount: '{$sAmountNet}',
quantity: '1',
descrMerchant: '{$sBasketItem.articlename}',
descrAffiliate: '{$sBasketItem.articlename}',
currency: '{$sBasketItem|currency:use_shortname:left}'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid={$sOrderNumber}&amp;tam={$sBasketItem.amount}&amp;data=&amp;qty=1&amp;descrMerchant={$sBasketItem.articlename}&amp;descrAffiliate={$sBasketItem.articlename}&amp;event=sales&amp;currency={$sBasketItem.additional_details.currency}" 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>

STEP 3 Save finish.tpl to your ftp account to the _yourtheme_local/frontend/checkout/ folder to complete and test the implementation.

When testing the campaign, please use the tracking test url you received from your account manager. If you did not receive this test url, please request this.

TRACKING GROUP ID EXAMPLE FOR IN FINISH.TPL
If you know what this is and if you have a tracking group ID, use this code, if you don't know what it is and do not have tracking group id, use the other code.

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '{$sOrderNumber}',
transactionAmount: '{$sAmountNet}',
quantity: '1',
descrMerchant: '{$sBasketItem.articlename}',
descrAffiliate: '{$sBasketItem.articlename}',
currency: '{$sBasketItem|currency:use_shortname:left}',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?tgi=[marker][/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid={$sOrderNumber}&amp;tam={$sBasketItem.amount}&amp;data=&amp;qty=1&amp;descrMerchant={$sBasketItem.articlename}&amp;descrAffiliate={$sBasketItem.articlename}&amp;event=sales&amp;currency={$sBasketItem.additional_details.currency}" 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>

ABOUT THE SHOPWARE TEMPLATE STRUCTURE
Best practice is to not make modifications to the actual template files, but to create a a local version of the template files you modified or want to modify. In Shopware you are able to create a local version of the template you are using by creating a folder in the template directory of your shop that starts with the name of the template followed by _local. The _emotion folder that is part of a default Shopware installation is the base emotion theme folder. As you can see in the templates folder on the ftp there are some variations on the emotion theme, for example emotion_black contains only some styling parts of the emotion theme. When a variation is selected in the back-end, the system will still check for modified files in _emotion_local folder and uses the files found as an override to the base theme folder.

Shopware template fallback method

_themename [Base template files]
_themename_local [Place to add modified theme files]
themename_somecolor [Independent variations on the theme]

This basically comes down to that the finish.tpl file that we want to modify must be in the folder /templates/_yourtheme_local/frontend/checkout/

HOW TO IDENTIFY THE USED TEMPLATE/THEME FOR YOUR SHOPWARE SYSTEM AND ADDING THE FINISH.TPL

1) Log in to the back-end of your shop and navigate to Configuration > Basic Settings > Shop settings > Templates to identify the active template.
2) Lets say you are using the theme yourtheme. Log in to your FTP account and navigate to the /templates/ folder .
3) Locate or create the folder /templates/_yourtheme_local/
4) Add the folder /frontend/ to /templates/_yourtheme_local/
5) Add the folder /checkout/ to /templates/_yourtheme_local/ frontend/
6) This folder structure will be in place: /templates/_yourtheme_local/frontend/checkout/
7) The location of finish.tpl will be like: /templates/_yourtheme_local/frontend/checkout/finish.tpl
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=25
14-Mar-2019 14:48:17
merchant JTL-Shop 3 Standard implementation You can use the filter options above to select your shop system, the version of your shop. The Version info selection is a short description of the implementation method we created for the shop you selected.

In order to get the redirecting to work correctly a .htaccess must be used for JTL implementations.

[marker]IMPORTANT! JTL uses template caching.[/marker]
When modifying a template file an old version of the file is used on the site. For example when making the modifications to the bestellabschluss_weiterleitung.tpl file a cached version of the file will remain in the /templates_c/ folder. The cached files can be found in /templates_c/yourTHEME/ and look similar to %%08^087^0877AC4B%%bestellabschluss_weiterleitung.tpl.php and should be removed in order for the modifications described here to have effect.

It is important to know exactly which template you are using for your site. The conversion script must be placed in the actual template structure in order to work!

The conversion script below must be added to the file /templates/[marker]YOURCURRENTTEMPLATE[/marker]/tpl_inc/bestellabschluss_weiterleitung.tpl from line 29 onward.

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales', // 'sales' or 'lead'.
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '{$Bestellung->cBestellNr}',
transactionAmount: '{$Bestellung->WarensummeLocalized[1]}',
quantity: '1', // Optional.
descrMerchant: '{$Bestellung->cZahlungsartName}',
descrAffiliate: '',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid={$Bestellung->cBestellNr}&amp;tam={$Bestellung->WarensummeLocalized[1]}&amp;data=&amp;qty=1&amp;descrMerchant={$Bestellung->cZahlungsartName}&amp;descrAffiliate=&amp;event=sales&amp;currency=" 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>

bestellabschluss_weiterleitung.tpl example
If you are not sure where to place the script exactly, you can download a bestellabschluss_weiterleitung.tpl example here.

After removing the cached file 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]=15
14-Mar-2019 14:47:37
merchant WooCommerce (WordPress) 1.6 - 2.0.x Overview WOOCOMMERCE v1.6 through v2.0.20 (WORDPRESS) TRADETRACKER CONVERSION IMPLEMENTATION

DO YOU USE A PAYMENT SERVICE PROVIDER? LIKE ICEPAY FOR EXAMPLE?
Using a Payment Service Provider can be a convenient option to handle the transactions that are done via your webshop. Please be aware that using a PSP in most cases requires additional work to set up our conversion registration mechanism correctly. A problem that we often see is that our implementation instructions are executed correctly, but when testing the campaign no transaction information is passed back to the actual order confirmation page on your website (where our conversion script is located). The general solution to this problem is to configure Payment Service Provider process in such a way that the PSP passes back the transaction information to the order success page on your website, that you are able to specify from within the PSP administration interface. The problem with this for us is that the process and available options are different for each Payment Service Provider.

WOOCOMMERCE IMPLEMENTATION
Login to your FTP account and open/edit the /wp-includes/functions.php file

Place the following code at the bottom of the function.php file Make sure to replace the CAMPAIGN_ID and PRODUCT_ID values within this code with the ones you received from TradeTracker:

function tradetracker($order_id)
{
$campaignID = '[marker]CAMPAIGN_ID[/marker]'; // Enter your campaignID as provided by TradeTracker.
$productID = '[marker]PRODUCT_ID[/marker]'; // Enter your productID as provided by TradeTracker.

// *****************
$order = new WC_Order($order_id);
$transactionID = htmlentities($order_id, ENT_QUOTES);
$transactionAmount = htmlentities((float) $order->order_total - (float) $order->order_shipping - (float) $order->order_discount - (float) $order->order_tax);

echo "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '{$campaignID}',
productID: '{$productID}',
transactionID: '{$transactionID}',
transactionAmount: '{$transactionAmount}',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: ''
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?cid={$campaignID}&amp;pid={$productID}&amp;tid={$transactionID}&amp;tam={$transactionAmount}&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency=\" 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>";
}

Open the /wp-content/plugins/woocommerce/woocommerce-hooks.php file and lookup the "Analytics" section.

Below the line "add_action( 'woocommerce_thankyou', 'woocommerce_ecommerce_tracking_piwik' );"
place the following piece of code:

add_action('woocommerce_thankyou', 'tradetracker');
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]=13
14-Mar-2019 14:47:21
merchant Plentymarkets All Standard implementation PLENTYMARKETS TRADETRACKER CONVERSION IMPLEMENTATION

You can use the filter options above to select your shop system, the version of your shop.
The Version info selection is a short description of the implementation method we created for the shop you selected.

STEP 1 - Download and upload the index.php redirect file to your PlentyMarkets FTP account

Seeing as PlenyMarkets is PHP capable 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 your PlentyMarkets FTP account.

Log in to the FTP account for your PlentyMarkets shop and locate the folder that looks like: /layout_some-name.plentymarket.net/

In this folder create a new folder and name it something that best represents your shop's content.

If you add the folder /layout_some-name.plentymarket.net/clothing/ for example, the link you should give to your account manager is:

http://www.yourplentyshopstore.net/layout/clothing/

This is the location from within a browser and this redirect location should be communicated to your account manager to set it in our system accordingly.


STEP 2 - Adding our conversion script to your PlentyMarket's order confirmation page

Log in to the Plentymarkets administration and go to Layout --> Layout-Generator --> Bestellbestätigung --> Tracking




The conversion script below must be added to the Body section of the tracking part.

In order to not mess up the code, you should select "Text field" from the dropdown on the right (as in the screenshot above).

Paste the following code within the body input field and press the Save icon.

TradeTracker TRACKING CODE to paste in the body section of Tracking

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales', // 'sales' or 'lead'.
campaignID: '[marker]CAMPAIGN_ID[/marker]', // The campaignID as provided by TradeTracker.
productID: '[marker]PRODUCT_ID[/marker]', // The productID as provided by TradeTracker.
transactionID: '[OrderID]', // Your internal and unique order identifier.
transactionAmount: '[ItemAmountNetDot]', // Format: 123.45. Set to zero in case of 'lead' event.
quantity: '1',
descrMerchant: '[CustomerID]-[ItemIDListPipe]', // Detailed description of the order. Optional.
descrAffiliate: '', // Description of the order. Optional.
currency: '[Currency]' // Use the ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Optional. Defaults to company currency if left empty.
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[OrderID]&amp;tam=[ItemAmountNetDot]&amp;data=&amp;qty=1&amp;descrMerchant=[CustomerID]-[ItemIDListPipe]&amp;event=sales&amp;currency=[Currency]" 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>

The campaign may now be tested.

MULTI COUNTRY CAMPAIGN CONVERSION CODE EXAMPLE FOR IN Layout --> Layout-Generator --> Bestellbestätigung --> Tracking --> Body

If you know what this is and if you have a tracking group ID, you can use this code, if you don't know what it is and do not have tracking group id, use the other code.

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales', // 'sales' or 'lead'.
campaignID: '[marker]CAMPAIGN_ID[/marker]', // The campaignID as provided by TradeTracker.
productID: '[marker]PRODUCT_ID[/marker]', // The productID as provided by TradeTracker.
transactionID: '[OrderID]', // Your internal and unique order identifier.
transactionAmount: '[ItemAmountNetDot]', // Format: 123.45. Set to zero in case of 'lead' event.
quantity: '1',
descrMerchant: '[CustomerID]-[ItemIDListPipe]', // Detailed description of the order. Optional.
descrAffiliate: '', // Description of the order. Optional.
currency: '[Currency]', // Use the ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Optional. Defaults to company currency if left empty.
trackingGroupID: '[marker][/marker]' // Only use in case it is set up by TradeTracker. Leave blank by default.
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?tgi=[marker][/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[OrderID]&amp;tam=[ItemAmountNetDot]&amp;data=&amp;qty=1&amp;descrMerchant=[CustomerID]-[ItemIDListPipe]&amp;event=sales&amp;currency=[Currency]" 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>

REDIRECT FOLDER NAMING CONSIDERATIONS
When creating the redirect folder keep the following things in mind. The index file functions as a "ghost" site that is visited (unseen by the visitor) to register the click from the affiliate to your site. This is also referred to as the redirect file/folder. The name of the redirect folder should represent the topic of your website as best way possible in one word or phrase.

DO NOT USE a name that resembles any connection or relation to tracking, TradeTracker, tt like:

www.yourwebsite.com/tt/
www.yourwebsite.com/tracking/
www.yourwebsite.com/tradetracker/
www.yourwebsite.com/redirect/

or anything similar because that can have an negative effect on the performance of the campaign you are about to set up, so just don't do it.

The name of the redirect folder should represent the contents of your website. If your site is selling fashion items or clothing for instance, you could NAME THE REDIRECT FOLDER something like:

www.yourwebsite.com/fashion/
or
www.yourwebsite.com/clothing/

or anything that best represents the content of your website.

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]=5
14-Mar-2019 14:47:08
merchant Drupal Commerce 7 Standard implementation IMPLEMENT DRUPAL COMMERCE TRADETRACKER TRACKING

Latest tested and verified version
Drupal 7.35 Install profile Commerce Kickstart (commerce_kickstart-7.x-2.22)

SETTING UP THE REDIRECT
Seeing as Drupal Commerce uses php you can download the redirect file here download index.php.

After downloading the index.php add your domainName to line 6.

After setting up the redirect for your campaign follow these steps in order to install our conversion registration within your Drupal Commerce environment.

COPY THIS CODE AND FOLLOW THE INSTRUCTIONS
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[commerce-order:order-number]',
transactionAmount: '[commerce-order:commerce-order-total:amount_decimal]',
quantity: '1',
descrMerchant: 'Internal orderID [commerce-order:order-id] | [commerce-order:owner]',
descrAffiliate: '',
currency: '[commerce-order:commerce-order-total:currency_code]'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[commerce-order:order-number]&amp;tam=[commerce-order:commerce-order-total:amount_decimal]&amp;data=&amp;qty=1&amp;descrMerchant=Internal orderID [commerce-order:order-id] | [commerce-order:owner]&amp;descrAffiliate=&amp;event=sales&amp;currency=[commerce-order:commerce-order-total:currency_code]" 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>

NOTE In case your CAMPAIGN ID and PRODUCT ID are not added to this example yet, they should be added manually.

Within the Drupal Commerce administration go to:

Store settings --> Advanced store settings --> Checkout settings --> 'Completion message' checkout pane:



Click the corresponding configure button and in the Checkout completion message input field add the script that is available on this page.

Please note to also select the Full HTML text format or the conversion registration will not work.



After adding the code and selecting Full HTML text format press Save configuration

The campaign is ready to be tested.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=41
14-Mar-2019 14:29:07
merchant WooCommerce (WordPress) 2.1 and higher Icepay Payment Service Provider Standard Implementation WOOCOMMERCE v2.1 AND HIGHER (ICEPAY) TRADETRACKER CONVERSION IMPLEMENTATION

Seeing as Wordpress / WooCommerce 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.

Please keep in mind that you will modify system files that can be overwritten when performing updates to the WooCommerce and / or Wordpress system files.

After updating system files you should always verify if the tracking is working. If the tracking is not working you should check the files that are used in this implementation and add our code again in case the files where updated.


ICEPAY IMPLEMENTATION
By default Icepay does not pass back the order amount to the specified return / success page that you can set within the Icepay administration interface.

Icepay suggests to use the Reference parameter that ís passed back to the order success page after a successful payment.

STEP 1 - SET THE ORDER AMOUNT IN THE REFERENCE PARAMETER FOR ICEPAY

The Reference parameter is part of icepay.php file that is located at /wp-content/plugins/icepay-woocommerce-online-payment-module/

Navigate to the above location and open and edit icepay.php. Within icepay.php (somewhere around line 717 or exactly on that line) you will find:

->setReference($orderID)
This must be changed to:

->setReference((float) ($ic_obj->amount - $shippingCosts - $orderDiscount) / 100)
After changing it. Save the modified icepay.php to your server.

STEP 2 - SET THE ORDER AMOUNT IN THE REFERENCE PARAMETER FOR ICEPAY
The TradeTracker conversion script must be added to the Wordpress theme you are using.

To do this you have 3 options.

OPTION 1
Check if the thankyou.php file is already part of the them you are using, by navigating to /wp-content/themes/YOURTHEME/woocommerce/checkout/thankyou.php

It's there? Open and edit it. The code below must be placed at the bottom of the thankyou.php file above the last php endif statement.

PASTE THIS CODE TO THANKYOU.PHP AT THE BOTTOM ABOVE THE LAST PHP ENDIF STATEMENT
<?php
$campaignID = 'CAMPAIGN_ID';
$productID = 'PRODUCT_ID';
$transactionID = empty($_GET['OrderID']) ? null : htmlentities($_GET['OrderID'], ENT_QUOTES);
$transactionAmount = empty($_GET['Reference']) ? null : htmlentities((float) $_GET['Reference'], ENT_QUOTES);
$descr = empty($_GET['PaymentMethod']) ? null : htmlentities($_GET['PaymentMethod'], ENT_QUOTES);
echo "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '{$campaignID}',
productID: '{$productID}',
transactionID: '{$transactionID}',
transactionAmount: '{$transactionAmount}',
quantity: '1',
descrMerchant: '{$descr}',
descrAffiliate: '',
currency: ''
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?cid={$campaignID}&amp;pid={$productID}&amp;tid={$transactionID}&amp;tam={$transactionAmount}&amp;data=&amp;qty=1&amp;descrMerchant={$descr}&amp;descrAffiliate=&amp;event=sales&amp;currency=\" 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>";
?>

Paste the code in thankyou.php directly ABOVE the last endif statement that is like:

<!-- CONVERSION CODE GOES HERE -->
<?php endif; ?>

OPTION 2
In case thankyou.php is not in the path /wp-content/themes/YOURTHEME/woocommerce/checkout/

You can choose to DOWNLOAD our preconfigured thankyou.php file (v2.0.0). This file already contains the our conversion registration code.

After downloading the file, open and edit the file and replace the first part of the code with:

$campaignID = 'CAMPAIGN_ID';
$productID = 'PRODUCT_ID';

Or you can add your ID's manually.

Save the thankyou.php file. Upload it to your theme's structure
at the following location: /wp-content/themes/YOURTHEME/woocommerce/checkout/

OPTION 3
If the thankyou.php file is not already in /wp-content/themes/YOURTHEME/woocommerce/checkout/

And if you prefer to use the current thankyou.php version from within your WooCommerce instalment's file structure.

Get the thankyou.php from it's default location, that is /wp-content/plugins/woocommerce/templates/checkout/thankyou.php

Download thankyou.php to your computer and edit it to add the conversion code as stated in OPTION 1.

When done. Add the modifed thankyou.php file to your theme's structure by uploading it to: /wp-content/themes/YOURTHEME/woocommerce/checkout/ (It might be that this path must be created manually)

IMPLEMENTATION SUMMARY

1) Add setReference information to icepay.php
2) Check the thankyou.php file to be part of your theme structure
3) Add the conversion script to the thankyou.php by choosing 1 of the suggested options and place it on your server

When the steps as described above are done 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]=36
14-Mar-2019 14:28:26
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: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=$productID&amp;tid=[marker]ORDER ID[/marker]&amp;tam=$transactionAmount&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency=" 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
14-Mar-2019 14:10:29
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: '',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[marker]ORDER_ID[/marker]&amp;tam=[marker]ORDER_AMOUNT[/marker]&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency=[marker]EUR[/marker]" 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]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[marker]{transactionID}[/marker]&amp;data=[marker][/marker]&amp;descrMerchant=&amp;descrAffiliate=&amp;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 varsValue(s)ExampleRequiredInfo
typesales or leadsalesYesDefine if the conversion is a sale or a lead.
campaignIDNumeric string1234YesYour campaign ID.The campaign ID as provided by TradeTracker.
productIDNumeric string4321YesYour product ID. The product ID as provided by TradeTracker.
transactionIDTextual stringABC-12345YesYour 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 string123.45Yes, 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'.
quantityNumeric string1NoIntended 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.
descrMerchantTextual stringSamsung UE55HU7500YesDetailed 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.
descrAffiliateTextual stringSamsung Ultra HD TVYesDescription of the order. Visible for affiliates only. Used by affiliates for campaign optimisation.
currencyTextual stringUSDNoCurrency 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.

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
14-Mar-2019 14:10:07
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: '',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?tgi=[marker][/marker]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[marker]ORDER_ID[/marker]&amp;tam=[marker]ORDER_AMOUNT[/marker]&amp;data=&amp;qty=[marker]1[/marker]&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency=[marker]EUR[/marker]" 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]&amp;pid=[marker]PRODUCT_ID[/marker]&amp;tid=[marker]ORDER_ID[/marker]&amp;data=&amp;descrMerchant=&amp;descrAffiliate=&amp;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 variablesPossible value(s)ExampleRequiredDescription
typesales or leadsalesYesDefine if the conversion is a sale or a lead.
campaignIDNumeric string1234YesYour campaign ID.The campaign ID as provided by TradeTracker.
productIDNumeric string4321YesYour product ID. The product ID as provided by TradeTracker.
transactionIDTextual stringABC-12345YesYour 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.
transactionAmountNumeric string123.45Yes, 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'.
quantityNumeric string1NoIntended 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.
descrMerchantTextual stringSamsung UE55HU7500YesDetailed 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.
descrAffiliateTextual stringSamsung Ultra HD TVYesDescription of the order. Visible for affiliates only. Used by affiliates for campaign optimisation.
currencyTextual stringUSDNoCurrency 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.
trackingGroupIDNumeric string11Leave blank by default unless instructed to do otherwise by TradeTracker Used to group campaigns for multiple countries.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=29
14-Mar-2019 14:08:18
merchant Shopify All Standard implementation Login to the Shopify administration backend.

Go to Settings --> Checkout --> Order processing --> Additional content & scripts

Paste the script below to the Additional content & scripts input field.

{% for line_item in line_items %}
<script type="text/javascript">
var price = parseFloat('{{ line_item.line_price | money_without_currency | replace: '.', '' | replace: ',', '' }}') || 0;
var discount = parseFloat('{{ line_item.discounts | money_without_currency | replace: '.', '' | replace: ',', '' }}') || 0;

var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: 'CAMPAIGN_ID',
productID: 'PRODUCT_ID',
transactionID: '{{ order_number }}',
transactionAmount: (price - discount) / 100,
quantity: '1',
descrMerchant: '{{ line_item.sku }}',
descrAffiliate: '{{ line_item.sku }}',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=CAMPAIGN_ID&amp;pid=PRODUCT_ID&amp;tid={{ order_number }}&amp;tam={{ line_item.line_price | money_without_currency }}&amp;data=&amp;qty=1&amp;descrMerchant={{ line_item.sku }}&amp;descrAffiliate={{ line_item.sku }}&amp;event=sales&amp;currency=EUR" alt="" />
</noscript>
{% endfor %}
<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>


Click Save to save the configuration.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=42
14-Mar-2019 14:07:07
merchant WooCommerce (WordPress) 2.1 and higher Multi country solution with tracking group ID WORDPRESS WOOCOMMERCE v2.1 MULTI COUNTRY | TRACKING GROUP ID IMPLEMENTATION

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 to use 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.

Because of the way that the tracking group functions it does not matter what product group is used, because it is impossible to know upfront to which campaign the order will be accounted to.

That is the reason that the product ID is not part of the script below. Only 1 valid campaign ID is needed in order for the script to function.

The script should be added to your WordPress WooCommerce installation as is.

Please keep in mind that you will modify system files that can be overwritten when performing updates to the WooCommerce and / or Wordpress system files.

After updating system files you should always verify if the tracking is working. If the tracking is not working you should check the files that are used in this implementation and add our code again in case the files where updated.


Login to your FTP account and open/edit the /wp-includes/functions.php file

Place the following code at the bottom of the functions.php file Make sure to replace the CAMPAIGN_ID and PRODUCT_ID values within this code with the ones you received from TradeTracker:

function tradetracker_tracking($order_id)
{
$campaignID = '[marker]CAMPAIGN_ID[/marker]';
$trackingGroupID = '[marker][/marker]';

// *****************
$order = new WC_Order($order_id);
$transactionID = htmlentities($order_id, ENT_QUOTES);
$transactionAmount = htmlentities((float) $order->order_total - (float) $order->order_shipping - (float) $order->order_discount - (float) $order->order_tax);
$currencycode = $order->order_currency;

echo "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
campaignID: '{$campaignID}',
trackingGroupID: '{$trackingGroupID}',
productID: '',
transactionID: '{$transactionID}',
transactionAmount: '{$transactionAmount}',
type: 'sales',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: '{$currencycode}'
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?tgi={$trackingGroupID}&amp;pid=&amp;tid={$transactionID}&amp;tam={$transactionAmount}&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency={$currencycode}\" 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>";
}

add_action( 'woocommerce_thankyou', 'tradetracker_tracking' );

Open the /wp-content/plugins/woocommerce/includes/wc-template-hooks.php file and lookup the "Order details" section.


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]=40
14-Mar-2019 14:06:47
merchant WooCommerce (WordPress) 2.1 and higher Standard implementation WOOCOMMERCE v2.1 AND HIGHER (WORDPRESS) TRADETRACKER CONVERSION IMPLEMENTATION

DO YOU USE A PAYMENT SERVICE PROVIDER?
Using a Payment Service Provider can be a convenient option to handle the transactions that are done via your webshop. Please be aware that using a PSP in most cases requires additional work to set up our conversion registration mechanism correctly. A problem that we often see is that our implementation instructions are executed correctly, but when testing the campaign no transaction information is passed back to the actual order confirmation page on your website (where our conversion script is located). The general solution to this problem is to configure Payment Service Provider process in such a way that the PSP passes back the transaction information to the order success page on your website, that you are able to specify from within the PSP administration interface. The problem with this for us is that the process and available options are different for each Payment Service Provider.

ICEPAY (WITHIN WORDPRESS / WOOCOMMERCE)
Our Wordpress, WooCommerce with ICEPAY solution is available here.

SETTING UP THE REDIRECT
Seeing as Wordpress / WooCommerce 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.

STANDARD WOOCOMMERCE TRADETRACKER IMPLEMENTATION

Please keep in mind that you will modify system files that can be overwritten when performing updates to the WooCommerce and / or Wordpress system files.

After updating system files you should always verify if the tracking is working. If the tracking is not working you should check the files that are used in this implementation and add our code again in case the files where updated.


Login to your FTP account and open/edit the /wp-includes/functions.php file

Place the following code at the bottom of the functions.php file Make sure to replace the CAMPAIGN_ID and PRODUCT_ID values within this code with the ones you received from TradeTracker:

function tradetracker_tracking( $order_id ) {

$campaignID = 'CAMPAIGN_ID';
$productID = 'PRODUCT_ID';

// *****************
$order = new WC_Order($order_id);
$transactionID = htmlentities($order_id, ENT_QUOTES);
$transactionAmount = htmlentities((float) $order->order_total - (float) $order->order_shipping - (float) $order->order_shipping_tax - (float) $order->order_discount - (float) $order->order_tax);
$currencycode = $order->order_currency;

echo "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '{$campaignID}',
productID: '{$productID}',
transactionID: '{$transactionID}',
transactionAmount: '{$transactionAmount}',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
currency: '{$currencycode}'
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?cid={$campaignID}&amp;pid={$productID}&amp;tid={$transactionID}&amp;tam={$transactionAmount}&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency={$currencycode}\" 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>";
}

add_action( 'woocommerce_thankyou', 'tradetracker_tracking' );


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]=35
14-Mar-2019 14:04:15
merchant Tracking SDK 1.0 Android TradeTracker SDK provides functionalities to track statistics of app install, usage, leads and sales generated from the app. The SDK is compatible with Android 4.0 (API version 14) and above. Android Studio is the recommended development environment.

Downloading the SDK
Download the SDK from following link: TradeTracker Android SDK

Importing the SDK
To import AAR file into your Android Studio project, go to File -> New -> Import module -> import JAR/.AAR package -> Select the path to AAR file -> select ‘Finish’.

To add a dependency to the SDK, go to Module Settings -> Select your app module -> Select dependencies tab -> Select ‘+’ option -> Module dependency -> Select the TradeTracker SDK -> select ‘OK’.

Using the SDK

Permissions
Update your project's AndroidManifest.xml file to include the INTERNET and ACCESS_NETWORK_STATE permissions.

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="your.app.package">

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

<application android:name="MyApplication">
...
</application>
</manifest>

INSTALL_REFERRER broadcast receiver
In the AndroidManifest.xml, add the following receiver as the FIRST receiver for INSTALL_REFERRER.
<application

[......]

<receiver
android:name="com.tradetracker.CampaignTrackingReceiver"
android:exported="true">
<intent-filter>
<action android:name="com.android.vending.INSTALL_REFERRER"/>
</intent-filter>
</receiver>

</application>

Note : If your app has multiple broadcast receivers for INSTALL_REFERRER action, then you can write a custom broadcast receiver which receives the INSTALL_REFERRER broadcast and passes the broadcast intent to all other receivers from different SDKs.
public class CustomBroadcastReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
CampaignTrackingReceiver tradeTrackerReceiver = new CampaignTrackingReceiver();
tradeTrackerReceiver.onReceive(context, intent);
}
}

Then in manifest file, you can add this as receiver for INSTALL_REFERRER action.
<application
[......]

<receiver
android:name="com.your.package.CustomBroadcastReceiver"
android:exported="true">
<intent-filter>
<action android:name="com.android.vending.INSTALL_REFERRER"/>
</intent-filter>
</receiver>

</application>

SDK initialization
Initialize the TradeTracker SDK in the Application class. This must be called before calling any other APIs on the shared singleton TradeTracker object.
public class MyApplication extends Application {

@Override
public void onCreate() {
super.onCreate();
TradeTracker.getInstance().init(this, "your-app-id");
}
}

SDK Logging (Optional)
You can enable the SDK logging to see the logs generated by the SDK during debugging. But remember to disable the logging before releasing the app.
TradeTracker.getInstance().enableLogging(LogLevel.DEBUG);
Installed Application
Deep linking has to be handled in your app to update the "referrer". In a case, if a user has already installed the app using an affiliate site and open the app using another affiliate site, the "referrer" has to be updated to get new MaterialID and AffiliateID. Following is an example;
import com.tradetracker.utility.Constants;
import com.tradetracker.utility.ParameterNames;
import com.tradetracker.utility.PreferenceUtility;
.....

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_detailed_tracking);

Intent intent = getIntent();
Uri data = intent.getData();

if(data != null && data.isHierarchical()){
String referrer = data.getQueryParameter(ParameterNames.REFERRER);
Context context = getApplicationContext();
if (!TextUtils.isEmpty(referrer)) {
PreferenceUtility.saveStoreReference(context, referrer);
TradeTracker.getInstance().trackAppStart();
}
}

initViews();
}


Tracking of the app start event
Track the app start in onCreate() function of the Launcher activity.
public class LauncherActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_launcher);

TradeTracker.getInstance().trackAppStart();;
}


Tracking of custom leads
To manually trigger a lead you can use the following API.
TradeTracker.getInstance().trackCustomLead(descrMerchant, descrAffiliate, eml, pid, tid);

Tracking of custom sales (in-app purchases)
To manually trigger a sale you can use the following API:
TradeTracker.getInstance().trackCustomSales(tam, descrMerchant, descrAffiliate, eml, pid, tid);

In addition to the parameters listed in the table above, you may pass on the order amount ("tam") as a Double, e.g. 123.45.


Testing
After the integration of the TradeTracker SDK, make sure that SDK receives the install referrer properly.

Testing install referrer by uploading a beta app to play store
You can upload a beta version of your app to google play store & use a sample advertising link to install the app.
Ex : https://play.google.com/store/apps/details?id=your.package.name&referrer={{MaterialID}}::{{AffiliateID}}
On the first launch of the app, SDK receives the install referrer info from play store & uses it as a param in subsequent events fired. Enable the SDK logging as described in section 2.4 to see the event logs generated by the SDK.

Testing install referrer with ADB
To verify that SDK is receiving the install referrer info properly, install your app in the device & run the following command in the Terminal:

adb shell am broadcast -a com.android.vending.INSTALL_REFERRER -n
com.your.package/com.tradetracker.CampaignTrackingReceiver --es
"referrer" "test_referrer_key=test_referrer_value"


Enable the SDK logging as described above to see the event logs generated by the SDK.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=45
05-Mar-2019 10:39:20
merchant Tracking SDK 1.0 iOS TradeTracker SDK provides functionalities to track statistics of app install, usage, leads and sales generated from the app.

Downloading the SDK
Download the SDK from following link: TradeTracker iOS Swift 2.2 SDK or TradeTracker iOS Swift 3.0 SDK

Importing the SDK
Add TradeTracker.framework to your Xcode project folder. Drag and drop TradeTacker.framework to your project workspace. Make sure that framework is added in embedded frameworks section in Xcode App Target -> General section.



Integrating with your app
Import TrackeTracker.framework in AppDelegate as shown in the snippets below.
Swift:
import TradeTracker
Objective C:
@import TradeTracker;

Initialize SDK in application:didFinishLaunchingWithOptions: method.
Swift:
func application(application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) ->
Bool {
TradeTrackerManager.startTradeTrackerManagerWithAppID("SomeAppID"
)
return true
}

Objective C:
- (BOOL)application:(UIApplication *)application
didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
[TradeTrackerManager startTradeTrackerManagerWithAppID:@"SomeAppID"];
return YES;
}


While integrating with Objective-C project you have to make sure that In Build settings->Build Options->‘Embedded Content contains Swift’ option is set as ‘Yes’.

Add a Run script in App TargetBuild Phases after embedded frameworks. Copy following code to to Run script

Strip framework:
bash "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/TradeTracker.framework/strip-frameworks.sh"



Now you have successfully integrated SDK to your App.

Logging
You can enable the SDK logging to see the logs generated by the SDK during debugging. But remember to disable the logging before releasing the app.
Swift:
TradeTrackerManager.logLevel = TradeTrackerLogLevel.Verbose
Objective C:
[TradeTrackerManager setLogLevel:TradeTrackerLogLevelVerbose];

Tracking
Tracking of Install
Swift
TradeTrackerManager.trackInstall()
Objective C
[TradeTrackerManager trackInstall];
Tracking of app start
Swift
TradeTrackerManager.trackStart()
Objective C
[TradeTrackerManager trackStart];
Tracking of custom leads
To manually trigger a lead you can use the following call:
Swift
TradeTrackerManager.trackCustomLead(descrMerchant: merchant, descrAffiliate: affiliate, email: email, pid: pid, tid: tid)
Objective C
[TradeTrackerManager trackCustomLeadWithDescrMerchant:merchant descrAffiliate:affiliate email:email pid:pid tid:tid];

Tracking of custom sales (in app purchases)
To manually trigger a sale you can use the following calls:
Swift
TradeTrackerManager.trackCustomSale(amount: amount, descrMerchant:merchant, descrAffiliate: affiliate, email: email, pid: pid, tid: tid)
Objective C
[TradeTrackerManager trackCustomSaleWithAmount:amount descrMerchant:merchant descrAffiliate:affiliate email:email pid:pid tid:tid];

In addition to the above parameters in the table, you may use the amount as DecimalNumber (e.g. 123.45).
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=62
05-Mar-2019 10:37:30
merchant PrestaShop 1.5 and higher Extension PRESTASHOP 1.5+ TRADETRACKER CONVERSION IMPLEMENTATION

TradeTracker.com Conversion Tools Module
To get the tracking up and running in a few steps, you may purchase and install the TradeTracker.com Conversion Tools module from the PrestaShop addon market place

This module will automatically install DirectLinking, conversion tracking and optionally the automatic assessment of orders generated through the TradeTracker.com network.

After purchase and install, login to your PrestaShop Administration and go to: Modules --> Advertising and Marketing --> TradeTracker Conversion Tools

If the status of our plugin is "Not Installed" click install and then configure. You will be presented with the TradeTracker configuration options (see the screenshots below).

Note that TradeTracker's DirectLinking is automatically set up for your shop. Please communicate this URL to your account manager.

The next step is to enter your Campaign ID ([marker]CAMPAIGN_ID[/marker]) and Product ID ([marker]PRODUCT_ID[/marker]) within the TradeTracker Tracking settings.

If requested to do so by your account manager enter the appropriate Tracking Group ID , otherwise you may leave it blank.

When the required information is entered click Save.

The campaign can now be tested by using the tracking test URL. For exact instructions on how to test, please consult your account manager.

TRADETRACKER AUTOMATIC ASSESSMENT SETTINGS
It is possible to automatically let your PrestaShop system assess orders within your TradeTracker.com dashboard. In short, it means that transactions will automatically be approved or rejected within your TradeTracker.com account, based on your order management actions within your PrestaShop interface. An example of that flow is as follows:

For this to work, you will need your TradeTracker API customer ID and passphrase. You can find these credentials by logging onto your TradeTracker account and navigating to:

General -> Account -> Web Services.

Within the "Access" pane on the right you will find your credentials. You may need to request access first by clicking the "request access" link.

PRESTASHOP 1.6 TRADETRACKER CONVERSION TOOLS EXAMPLE



PRESTASHOP 1.5 TRADETRACKER CONVERSION TOOLS EXAMPLE

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=11
17-Jan-2019 11:51:12
merchant General All Deduping between networks Deduping between networks
Regular click to conversion route with one network
A normal click to conversion route would look similar to the following:



Regular click to conversion route with multiple networks
When a campaign is active within multiple networks, a click to conversion route would look similar to:



In the above example, without deduping, the conversion would be registered within both networks and the merchant would manually need to check which network delivered the last click to attribute the commission correctly.

A deduping script however would allow for this to be done automatically.

How to implement a dedupe script
A dedupe script works twofold: first a script needs to set a dedupe cookie which stores through which network the visitor landed on your page. A second script on the confirmation page, which holds all network tracking scripts, checks the value of this cookie and fires only that specific script.
A fallback method should also be installed which makes sure that all pixels are fired in case cookies have been deleted by the user. This fallback method should append something like “_fallback” to the order ID within the pixels so that the merchant may easily spot these fallback conversions within the dashboard of each individual network.

Setting the dedupe cookie
In order to store the actual last click from a specific network, a parameter like “network” can be used. Each network would need to attach “network=NETWORK_NAME” to each incoming link to the merchant’s site, e.g. http://merchant.com/?network=tradetracker A server side script can then set a cookie based on that parameter and its value. In PHP for example:

if (!empty($_GET['network']))
setcookie('network', trim($_GET['network']), strtotime('+100 days'), '/', '.merchant.com');


The last value, “.merchant.com” should be replaced by the domain name on which the script runs. Don’t forget to include the dot in front of the domain name.

The dedupe script on the confirmation page
Once the confirmation page is loaded and the network pixel needs to be fired, a small script reads the cookie created during the click and checks its value. It then uses this value to switch to the correct pixel. In case the cookie was deleted somehow, a fallback method should be executed. Here’s a PHP example:

$pixels = array(
'tradetracker' => '<img />',
'network1' => '<img />',
'network2' => '<img />',
'network3' => '<img />'
);

if (!empty($_COOKIE['network']) && array_key_exists($_COOKIE['network'], $pixels))
echo $pixels[$_COOKIE['network']];
else
foreach ($pixels as $pixel)
echo $pixel, PHP_EOL;


In the above example, you would need to specify each pixel from the respective networks.

TradeTracker’s readymade script
There is also a possibility that you use TradeTracker’s readymade JavaScript solution to handle the deduping of the conversions. As with a custom built solution, you would need to inform the networks first which parameter and value they would need to attach to each link. Within this example we will use “network” as parameter name.

Include the following script on each page within your website, except the confirmation page:

<!-- Begin TradeTracker Dedupe Code -->
<script>
(function() {
var tt = document.createElement('script');
tt.type = 'text/javascript'; tt.async = true;
tt.src = '//sc.tradetracker.net/tracker/merchant?e=dd&t=js';

tt.addEventListener('load', function() {
_ttDedupe(
'click',
'network'
);
});

var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
})();
</script>
<!-- End TradeTracker Dedupe Code -->


To get this code to display on each page, you would normally place this code in the same centralised file as for example Google Analytics.

Note that the second parameter within the _ttDedupe function is the actual name of the parameter used within all networks. By default it’s named “network”, but can basically be anything you like as long as it consists of the characters a-z, A-Z, 0-9 dashes and pipelines. In case you do decide to use another name for this parameter, be sure to inform your networks.

On the confirmation page you should then use the following script:

<!-- Begin TradeTracker Dedupe Code -->
<script>
// The pixels.
var _oPixels = {
tradetracker: '<img id="tradetracker" />',
network1: '<img id="network1" />',
network2: '<img id="network2" />',
network3: '<img id="network3" />'
};
</script>
<noscript>
<img id="tradetracker" />
<img id="network1" />
<img id="network2" />
<img id="network3" />
</noscript>
<script>
(function() {
var tt = document.createElement('script');
tt.type = 'text/javascript'; tt.async = true;
tt.src = '//sc.tradetracker.net/tracker/merchant?e=dd&t=js';

tt.addEventListener('load', function() {
_ttDedupe(
'conversion',
'network'
);
});

var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
})();
</script>
<!-- End TradeTracker Dedupe Code -->


The “_oPixels” object contains the names and the corresponding pixels of each network. These are also the values that should be used by the networks for the parameter that is attached to each individual link, e.g. network=tradetracker.

Also, within the “noscript” tags all the images should be placed for the sporadic case in which a visitor has JavaScript disabled.

[marker]Note: be careful when copying the aforementioned code. Do not copy the line numbers into your actual page. Also, please pay very close attention to the line numbers: make sure that in case a line of code is broken down into multiple lines in the code above, the code eventually should be on one line in your file.[/marker]
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=44
26-Sep-2017 16:21:26
merchant Magento 1.7 - 1.9 Extension module MAGENTO v1.7 - v1.9 TRADETRACKER CONVERSION TOOLS EXTENSION INSTALLATION AND CONFIGURATION INSTRUCTIONS

SETTING UP THE REDIRECT
Seeing as Magento uses php you can download the redirect file here download index.php.

After downloading, please add your domainName to line 6. After setting up the redirect for your campaign you can follow these steps in order to install our Magento plugin.

GETTING THE MAGENTO TRADETRACKER CONVERSION TOOLS EXTENSION
For Magento 1.7.0.0 and higher we offer a paid extension package which will install the conversion tracking automatically within your webshop system.

Purchase Plugin | € 39.99

After requesting the plugin, please allow 1-2 working days for delivery by your account manager.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=4
03-Jul-2017 18:23:17
merchant OpenCart 2.3.0+ Extension module OPENCART 2.3.0+ TRADETRACKER CONVERSION IMPLEMENTATION

TradeTracker.com Conversion Tools Module
To get the tracking up and running in a few steps, you may purchase and install the TradeTracker.com Conversion Tools module from the OpenCart market place.

This module will automatically install DirectLinking, conversion tracking, a product feed and optionally the automatic assessment of orders generated through the TradeTracker.com network.

The detailed and easy to read documentation required to get started is included within the package.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=34
21-Mar-2017 10:49:02