SC - Implementation overview

Target group

Name

Version

Version info

Implementation steps

Last modified

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 15:51:40

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

<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>

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=21

14-Mar-2019 15:53:44

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 variables	Possible value(s)	Example	Required	Description
type	sales or lead	sales	Yes	Define if the conversion is a sale or a lead.
campaignID	Numeric string	1234	Yes	Your campaign ID.The campaign ID as provided by TradeTracker.
productID	Numeric string	4321	Yes	Your product ID. The product ID as provided by TradeTracker.
transactionID	Textual string	ABC-12345	Yes	Your shop's internal and unique order identifier. The transaction identifier (e.g. orderID) is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution.
transactionAmount	Numeric string	123.45	Yes, if type is 'sales'.	Transaction amount variable. The transaction amount is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. In case of a lead campaign this can be left blank or set to '0'.
quantity	Numeric string	1	No	Intended for statistical analysis in future software releases. You are able to specify the quantity of the order here. Currently this does not affect the registration of the order, in the future this will be used to be able to calculate the order amount for example (if this has added value for you) and it will be used for statistical information.
descrMerchant	Textual string	Samsung UE55HU7500	Yes	Detailed description of the order. Used for statistical purposes. Visible for the merchant only. You can add variable values here and/or other order information you might want to see in your TradeTracker account. Use this to add product information or order information.
descrAffiliate	Textual string	Samsung Ultra HD TV	Yes	Description of the order. Visible for affiliates only. Used by affiliates for campaign optimisation.
currency	Textual string	USD	No	Currency of the transaction. ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Defaults to company currency if left empty. Also used in combination with our automatic currency conversion option This option is turned off by default. Ask your account manager if you need this option to be activated.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=2

14-Mar-2019 15:56:18

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

23-Sep-2019 13:03:14

merchant

General

All

Redirect

IMPLEMENTING TRADETRACKER REDIRECT AND CONVERSION INSTRUCTIONS AND CONSIDERATIONS
The articles on these pages are created to help you implement our tracking and conversion registration method.

If you arrived at this portal by using a link that was sent to you, we would like to inform you about the accompanying document to these pages.
This document contains more or less similar information as to be found on this site, but is structured chronological and contains links to the relevant pages on this site, making it somewhat easier to read, depending on what you prefer.
The document is part of the start mail you received or available in your account.

Implementing our click registration and conversion tracking should take about 30 minutes up to 2 hours for general situations.
Although it can be done in 15 minutes in case you are already familiar with setting it up using an available pre-configured implementation method and if there are no unexpected surprises. It can however be longer in more complex set-ups with more stakeholders or when encountering other problems.

We highly recommend you to read the information in the document or on this site.
These articles contain important information about how, why and what you should do in order to set up your campaign successfully.

Setting up the TradeTracker tracking consists of 2 parts:
1) Registering a click from the affiliate’s website to your site.
2) Registering resulting conversions to be able to match the click to the sale.

In order to be able to implement our tracking system, you must be able to:
1) Create a redirect location on your (sub) domain.
2) Make modifications to the checkout success / order confirmation page of your web shop system.

The first thing that needs to be done is getting the click registration mechanism to work.
The redirect is based on creating a location on your domain which will handle all incoming clicks from your affiliates. This can be done by either creating a separate rewrite path or physical directory and making one of our redirect example code files available to handle the incoming clicks. Optionally, you may also create a subdomain (e.g. offers.merchant.com) and making the desired redirect available within the root of your subdomain. This is the preferable method in case you want to keep this implementation separate from your regular developments on your main domain.

The available languages we offer are ASP (.asp) | Coldfusion (.cfm) | CSHARP (.aspx) | JSP (.jsp) | PERL (.pl) | PHP (.php) | Python (.py) | Visual Basic ASPX (.aspx).

DOWNLOAD THE AVAILABLE REDIRECT REDIRECT SCRIPT EXAMPLES HERE and extract the zip-file to your computer.

The zipped file contains directorys that represent the programming language of the redirect script example. You should choose an redirect script example in a language (extension) that is supported by your server.

ADD YOUR DOMAIN NAME TO THE INDEX REDIRECT FILE
The redirect script example to use depends on the type of server and the programming language that is supported by your server.
To make sure our tracking is working as intended, the domain of your website (without www. ) must be added to the redirect file. Check the file for the "domainName" variable and change to your main domain accordingly.
If your shop is running on www.merchant.com or shop.merchant.com for example, the domainName value to enter would be "merchant.com".

By default the redirect script example we provide should work in most situations. They are created, tested and verified to work for the majority of our clients. We do not encourage further modification of the provided redirect script example, unless you have a very good reason to do so and know exactly what you are doing.

MAKING THE REDIRECT AVAILABLE
Within the introduction e-mail that you received from your account manager a suggestion for the location of the redirect location is made. If you decide to use an other location, please communicate this to your account manager because the correct location is needed to get your campaign to work as intended.

CHOOSING A LOCATION FOR THE REDIRECT
The redirect location name should be a phrase that best represents your shop or topic of your site. If you have a website that sells fashion items or clothing, the name of the redirect directory should represent this. For instance in this case it might be www.yourwebsite.com/fashion/ or www.yourwebsite.com/clothing/.

Please refrain from using a name that resembles any connection or relation to TradeTracker like www.yourwebsite.com/tt/ www.yourwebsite.com/tracking/ www.yourwebsite.com/tradetracker/ or www.yourwebsite.com/redirect/ for example.

You should verify that the suggested directory is not already part of your website’s link structure. This can be the case if URL rewriting is used for the suggested directory and content is already attached to the suggested location. If that is the case, please think of an alternative location/directory to place the redirect file.

Turn URL rewriting off in case you use an actual "physical" directory
In case your site is using URL rewriting to create pretty links on your website, URL rewriting must be turned off for the redirect directory in order for it to work correctly. This is done in different ways for different server environments. On an Apache web server, the URL rewrite engine can be turned off for a specific directory by placing an .htaccess file within the redirect directory containing the line:

RewriteEngine Off
For more information about URL rewriting and links to different server settings we refer you to Wikipedia - URL Rewrite Engine.

In case your server supports .htaccess files you can download a zipped .htaccess file to use here.

SUMMARY TO SET UP THE REDIRECT LOCATION

1. Determine the server environment and choose the programming language format accordingly (or create one based on one of the example codes)
2. Create the redirect location (either a rewrite, physical directory or subdomain)
3. Set the domainName variable with your main domain (without www.) in the redirect script example
4. Make the redirect script publicly available at the chosen location and if using an actual physical directory, turn off the URL rewrite engine according to your server configuration options
5. Use the tracking test URL that corresponds to the redirect location to test the redirect

When these steps are done, you are ready to test the redirect to your site by using the tracking test link.

If you did not receive the tracking test link or used a different then suggested redirect location, please contact your account manager.

SETTING UP THE TRADETRACKER CONVERSION SCRIPT AND IMPLEMENTATION CONSIDERATIONS
Before you start copying and pasting the codes that can be found by clicking the links below to your site and come to the conclusion that it's not working as you had planned, please hold on to your horses. Implementing our conversion script requires some thought and consideration. The reason for this is that there are a lot of options and configuration situations to take into account.

Do you have a custom built website? If so, what program language is used? Do you use a Payment Service Provider? An existing web shop system? Are for example things that influence the technical implementation strategy to follow.

We have described a couple of things for you to consider or determine before continuing the implementation.

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

PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS
click the link above to see if we have a solution for your environment available.
The advantages are that these solutions are already configured to use the correct variable values and tested in a default installation of the web shop system.

OUR UNIVERSAL CONVERSION SCRIPTS.
Our universal script is the script that we use to create the web shop specific solutions.
The script requires the variable values that are needed to register conversions within our system to be added manually, but it can be used for any situation.
It does require some basic programming knowledge of the environment in which the script must be placed or use the supported variable placeholders of your shop or environment.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=1

30-Jul-2020 14:01:11

merchant

General

All

Server to Server (S2S) tracking

Setting up Server to Server (S2S) tracking
Server to server tracking is used in situations where regular conversion registration is not possible by means of placing our tracking code within the publicly available pages on your website (known as "client-side tracking"). The S2S method relies on a unique click identifier to be stored on your server and passed back at the time of the conversion.

We are able to pass our unique click identifier to each page on your website and you are free to choose exactly what the name of this parameter should be, e.g. "someparameter".

The tracking data value is a unique reference to identify clicks within our system and is unique for each incoming click on your website.

As a result, a link to one of your landing pages will look something like:

http://yourwebsite.com/landing/page?someparameter=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker]
Please note we always send this parameter url-encoded. Also, it's important this value is stored somewhere within a storage of choice, e.g. a memory database and/or a relational database, depending on the usage. When using a database, it can for example be stored within a column ttClickID or any other column name you prefer.

How to pass back the click identifier
Whenever a conversion is triggered for which an affiliate should receive a reward, this click identifier should be passed back to TradeTracker.
One of the tasks that lies ahead for your development team, is to store this unique click identifier, together with the information that is used to trigger this conversion.

Example
Let's assume you run an online gaming website and you reward affiliates for bringing in new players. It's important that our unique click identifier is stored together with the new player information so that it can be accessed at the time of conversion trigger.

Within a database it would look something like:

id	name	user	eml	regdate	ttClickID
111	J. Smith	jsmith00	jsmith@eml.net	2014-09-01	[marker]0::12345::abc::::1405418672[/marker]
112	J. Doe	player123	doe.j@email.org	2014-09-02	12::54321::def::::1405419867

LEAD CONVERSION CALLBACK
In case an event is triggered that resembles a lead conversion (e.g. user registration), the following callback format is used:

https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&data=[marker]{ttClickID}[/marker]&vc={voucherCode}

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

https://ts.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&tam={transactionAmount}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&currency={currency}&data=[marker]{ttClickID}[/marker]&vc={voucherCode}

In the above callbacks the {ttClickID} is tied to a fixed "data" parameter and its value must be replaced by the value saved during the initial click (and eventually stored within a database, like the table above).

Note: Please make sure all values are URL-encoded.

Example formatted callback

https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid=123456&descrMerchant=new%20player&descrAffiliate=new%20player&data=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker]

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=31

30-Nov-2021 17:07:39

merchant

WP WooCommerce extension

1.x

Generic

Please note that Version 2.x is available now.
To ensure a seamless experience, make sure to implement the most recent version via the following guide: Version 2.x

In order to get the TradeTracker implementation up and running seamlessy with WooCommerce, you may add the TradeTracker WooCommerce Extension manually to your WP installation.

The zip-file in question may be found within your merchant dashboard under the "Support" heading at the top of the page:

Once you have downloaded the zip file, upload it to your Wordpress Plugins section by clicking the "Add new" button:

In the subsequent screen, click the "Upload Plugin" button and upload the above downloaded zip file:

This is also they way-of-working in case you're updating an existing TradeTracker WooCommerce plugin with a new version.

After a successful upload, head over to your plugins section and activate the plugin if not already done by clicking the "Activate" link:

After the plugin has successfully been activated, click "Settings":

On the subsequent page, enter your "Campaign ID" and "Product ID" as received from TradeTracker.

Optionally, you may enter a "Tracking Group ID" but only if explicitly instructed by TradeTracker to enter a value for it. If not, you may leave it blank.

Save these settings and you're good to go!

Now, please test the implementation together with your account manager.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=72

06-Dec-2021 16:46:35

merchant

Magento

Plugin

1.x - 2.x

MAGENTO CONVERSION IMPLEMENTATION

In order to get tracking up and running swiftly within your Magento webshop, we gladly point you to the available plugins.
Provided below are plugins for Magento version 1.7.2 - 1.9.X, as well as a plugin for Magento versions 2.3 - 2.X.

Magento version 2

Magento version 1 by third party Magmodules.eu.
For support, please refer to Magmodules in case you might run into configuration issues. Their professional support has short response times.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=70

15-Dec-2021 16:39:24

merchant

General

All

Multi country campaign conversion script

MULTI COUNTRY CAMPAIGN CONVERSION SCRIPTS
TradeTracker campaigns get a unique campaign ID per country in which the campaign will be active. The Tracking Group ID is used to be able to use just 1 general conversion script on your confirmation page, instead of a script for each country in which the campaign is active. The way that this works is that our system will check for each campaign within the tracking group where the originating click came from and assigns any resulting conversions to the correct campaign in the correct country.

The multi-country conversion script should only be used after receiving a Tracking Group ID from your account manager.

Please note that the script you choose below must contain 1 of your campaign ID's (in general just the main campaign ID) in order for the conversion scripts to work.

The campaign ID that is added is only used to check if the main campaign is active, the tracking group number is used to assign the conversion to the correct campaign in our system.

MULTI COUNTRY CAMPAIGN SALES CONVERSION SCRIPT

<script type="text/javascript">
 var ttConversionOptions = ttConversionOptions || [];
 ttConversionOptions.push({
  type: 'sales',
  campaignID: '[marker]CAMPAIGN_ID[/marker]',
  productID: '[marker]PRODUCT_ID[/marker]', 
  transactionID: '[marker]ORDER_ID[/marker]', 
  transactionAmount: '[marker]ORDER_AMOUNT[/marker]', 
  quantity: '1', 
  descrMerchant: '', 
  descrAffiliate: '',
  currency: '', 
  vc:'',
  trackingGroupID: '[marker][/marker]' 
 });
</script>
<noscript>
 <img src="//ts.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&tam=[marker]ORDER_AMOUNT[/marker]&data=&qty=1&descrMerchant=&descrAffiliate=&event=sales&currency=[marker]EUR[/marker]&vc=" alt="" />
</noscript>
<script type="text/javascript">
  // No editing needed below this line.
 (function(ttConversionOptions) {
  var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null);
  var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m';
  var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
 })(ttConversionOptions);
</script>

MULTI COUNTRY CAMPAIGN LEADS CONVERSION SCRIPT

<script type="text/javascript">
 var ttConversionOptions = ttConversionOptions || [];
 ttConversionOptions.push({
  type: 'lead', 
  campaignID: '[marker]CAMPAIGN_ID[/marker]', 
  productID: '[marker]PRODUCT_ID[/marker]', 
  transactionID: '[marker]ORDER_ID[/marker]', 
  descrMerchant: '', 
  descrAffiliate: '', 
  trackingGroupID: '[marker][/marker]'
 });
</script>
<noscript>
 <img src="//tl.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&data=&descrMerchant=&descrAffiliate=&event=lead" alt="" />
</noscript>
<script type="text/javascript">
  // No editing needed below this line.
 (function(ttConversionOptions) {
  var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null);
  var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m';
  var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
 })(ttConversionOptions);
</script>

OUR UNIVERSAL CONVERSION SCRIPTS
PRE-CONFIGURED WEB SHOP CONVERSION IMPLEMENTATION SOLUTIONS
SETTING UP THE REDIRECT INSTRUCTIONS
IMPLEMENTATION CONSIDERATIONS

VARIABLES OVERVIEW AND DESCRIPTIONS

Available variables	Possible value(s)	Example	Required	Description
type	sales or lead	sales	Yes	Define if the conversion is a sale or a lead.
campaignID	Numeric string	1234	Yes	Your campaign ID.The campaign ID as provided by TradeTracker.
productID	Numeric string	4321	Yes	Your product ID. The product ID as provided by TradeTracker.
transactionID	Textual string	ABC-12345	Yes	Your shop's internal and unique order identifier. The transaction identifier (e.g. orderID) is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution.
transactionAmount	Numeric string	123.45	Yes, if type is 'sales'.	Transaction amount variable. The transaction amount is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. In case of a lead campaign this can be left blank or set to '0'.
quantity	Numeric string	1	No	Intended for statistical analysis in future software releases. You are able to specify the quantity of the order here. Currently this does not affect the registration of the order, in the future this will be used to be able to calculate the order amount for example (if this has added value for you) and it will be used for statistical information.
descrMerchant	Textual string	Samsung UE55HU7500	Yes	Detailed description of the order. Used for statistical purposes. Visible for the merchant only. You can add variable values here and/or other order information you might want to see in your TradeTracker account. Use this to add product information or order information.
descrAffiliate	Textual string	Samsung Ultra HD TV	Yes	Description of the order. Visible for affiliates only. Used by affiliates for campaign optimisation.
currency	Textual string	USD	No	Currency of the transaction. ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Defaults to company currency if left empty. Also used in combination with our automatic currency conversion option This option is turned off by default. Ask your account manager if you need this option to be activated.
trackingGroupID	Numeric string	11	Leave blank by default unless instructed to do otherwise by TradeTracker	Used to group campaigns for multiple countries.
vc	Textual string	Welcome-123	No	The (main) discount code used for the order in question. Used in case you would like to work with unique voucher codes for certain publishers

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=29

29-Jul-2025 10:02:02

merchant

Shopify

All

Group basket items

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. Be sure to substitute the CAMPAIGN_ID and PRODUCT_ID values with the values received from TradeTracker.

<script type="text/javascript">
 var ttConversionOptions = ttConversionOptions || [];
 ttConversionOptions.push({
  type: 'sales',
  campaignID: 'CAMPAIGN_ID',
  productID: 'PRODUCT_ID',
  transactionID: '{{ order.order_number }}',
  transactionAmount: parseFloat({{ subtotal_price | divided_by: 100 }}) || 0,
  quantity: '1',
  descrMerchant: encodeURIComponent('Internal order ID: {{ order_id }}'),
  descrAffiliate: '',
  currency: '{{ checkout.currency }}',
  vc: '{{ checkout.discount_applications[0].title | escape }}',
  trackingGroupID: ''
 });
</script>
<noscript>
 <img src="//ts.tradetracker.net/?cid=CAMPAIGN_ID&tgi=&pid=PRODUCT_ID&tid={{ order.order_number }}&tam={{ subtotal_price / 100 }}&data=&qty=1&descrMerchant={{ transaction.gateway }}&descrAffiliate=&event=sales&currency={{ checkout.currency }}&vc={{ discount.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>

Click Save to save the configuration.

Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=71

29-Jul-2025 10:04:12