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