Target group Name Version Version info Implementation steps Last modified
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&amp;tgi=&amp;pid=PRODUCT_ID&amp;tid={{ order.order_number }}&amp;tam={{ subtotal_price / 100 }}&amp;data=&amp;qty=1&amp;descrMerchant={{ transaction.gateway }}&amp;descrAffiliate=&amp;event=sales&amp;currency={{ checkout.currency }}&amp;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
18-Nov-2020 15:09:43
merchant Shopify All Split 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.

{% for line_item in line_items %}
<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: 'CAMPAIGN_ID',
productID: 'PRODUCT_ID',
transactionID: '{{ order.order_number }}',
transactionAmount: parseFloat({{ line_item.price - line_item.line_level_total_discount | divided_by: 100 }}) || 0,
quantity: '{{ line_item.quantity }}',
descrMerchant: encodeURIComponent('SKU: {{ line_item.sku }}'),
descrAffiliate: '',
currency: '{{ checkout.currency }}',
vc: '{{ line_item.discount_allocations[0].discount_application.title | escape }}',
trackingGroupID: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=CAMPAIGN_ID&amp;tgi=&amp;pid=PRODUCT_ID&amp;tid={{ order.order_number }}&amp;tam={{ line_item.price - line_item.line_level_total_discount | divided_by: 100 }}&amp;data=&amp;qty={{ line_item.quantity }}&amp;descrMerchant={{ line_item.sku }}&amp;descrAffiliate=&amp;event=sales&amp;currency={{ checkout.currency }}&amp;vc={{ line_item.discount_allocations[0].discount_application.title | escape }}" 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>


Hit the Save button to save the configuration.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=42
18-Nov-2020 15:09:13
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 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 11:37:30
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 Exclusive voucher codes EXCLUSIVE VOUCHER CODES

Exclusive voucher code tracking makes it possible for advertisers to make voucher codes in the TradeTracker interface exclusive for one affiliate. Although advertisers often hand out vouchers exclusively to one publisher, this feature offers full exclusivity. This implies that when the voucher is used by a consumer, the last touchpoint will always go to the exclusive affiliate. This means that even when another affiliate or website is communicating this voucher code and generates traffic using this voucher code, the last touchpoint will go to the publisher granted with the exclusivity.

If you are a new Advertiser, please proceed to our general conversion script page and implement the pixel.

If you are a existing Advertiser, please amend your conversion script with following (place in script that requires additions is marked):
- Add vc:'EXCLUSIVE_CODE', to conversion script
- Add &vc= parameter to image pixel

Note: EXCLUSIVE_CODE should be variable passed to the script from your system. It is case-sensitive and it should be passed from your voucher code field on checkout page.

Note 2: If you are using any form of deduplication, please make sure that our complete tracking script is always triggered if this exclusive voucher code is used by a consumer. Otherwise offline tracking will not be possible and the voucher will not be full-exclusive for the publisher.



<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: 'CAMPAIGN_ID',
productID: 'PRODUCT_ID',
transactionID: 'ORDER_ID',
transactionAmount: 'ORDER_AMOUNT',
quantity: '1',
descrMerchant: '',
descrAffiliate: '',
[marker]vc:[/marker]'[marker]EXCLUSIVE_CODE[/marker]',
currency: ''
});
</script>
<noscript>
<img src="//ts.tradetracker.net/?cid=CAMPAIGN_ID&amp;pid=PRODUCT_ID&amp;tid=ORDER_ID&amp;tam=ORDER_AMOUNT&amp;data=&amp;qty=1&amp;descrMerchant=&amp;descrAffiliate=&amp;event=sales&amp;currency=EUR[marker]&amp;vc=[/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>
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=69
07-Jun-2019 18:24:35
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 15:51:22
affiliate General All Custom clickout script Using a custom clickout script

As affiliate you can easily create a custom click out script which enables you to easily handle all kind of events like for example click registration or forwarding users from a secure (https) environment to a non-secure location.

In a PHP environment for example, you can create a page containing the following code:

<?php
if (!empty($_GET['url']))
{
// Your custom code here, e.g. click registration.
$x = new ClickHandler();
$x->saveClickToDatabase($_GET['url']);

// When done, forward to the requested location.
exit(header('Location: ' . $_GET['url'], true, 301));
}
?>

In this example a file called clickout.php is created and placed in the root folder of the website.

Links on your website would eventually look like:

<a href="https://yourwebsite.com/clickout.php?url=http%3A%2F%2Ftc.tradetracker.net%2F%3Fc%3D27%26m%3D0%26a%3D1">Clickout</a>
Please note that the value of the "url" parameter should always be URL-encoded according to official standards.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=38
05-Dec-2014 09:02:33
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 15:29:07
merchant Gambio (xt:Commerce) All Order registration per product including VAT GAMBIO 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.

Download the tradetracker.php file and upload it to the /includes/ folder, located in the root of your FTP account.

Locate checkout_success.php in the root of your account: /WEBROOT/checkout_success.php

Open the checkout_success.php file and within the code locate the following line:
[marker]$main_content = $smarty->fetch(CURRENT_TEMPLATE.'/module/checkout_success.html');[/marker]
Copy and paste the following code above the aforementioned highlighted line of code.

$tt_campaignID = '[marker]CAMPAIGN_ID[/marker]';
$tt_productID = '[marker]PRODUCT_ID[/marker]';
$tt_imageTag = include './includes/tradetracker.php';
$smarty->assign('tt_imageTag', $tt_imageTag);

Make sure to replace the campaignID and productID with the ID's you received from TradeTracker if they are not set in this example.

The result is as follows:
$tt_campaignID = '[marker]CAMPAIGN_ID[/marker]';
$tt_productID = '[marker]PRODUCT_ID[/marker]';
$tt_imageTag = include './includes/tradetracker.php';
$smarty->assign('tt_imageTag', $tt_imageTag);

[marker]$main_content = $smarty->fetch(CURRENT_TEMPLATE.'/module/checkout_success.html');[/marker]

LOCATE THE CHECKOUT SUCCESS HTML TEMPLATE
Locate the checkout_success.html file in the template folder you are using for your site. Normally the checkout_success.html template file is to be found in the following location:

/templates/{TEMPLATE_NAME}/module/checkout_success.html

IMPORTANT NOTICE It is important to use the template file of the actual template you are using for your site. If for example the template "EyeCandy" is used, the location of the checkout success file would be: /templates/EyeCandy/module/checkout_success.html

Copy and paste this piece of code at the bottom of the checkout_success.html template file:
<!-- TradeTracker conversion tracking start -->
{$tt_imageTag};
<!-- TradeTracker conversion tracking end -->

When done, upload or save the file to your server and overwrite the checkout_success.html file.

After these steps are performed, the campaign is ready to be tested. Make sure you use the TradeTracker Tracking Test URL before doing the test. If you don’t have the test URL, please ask your account manager to provide it to you.

Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=9
05-Dec-2014 09:23:16
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 15:47:37
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 11:49:02
merchant osCommerce All 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.

SETTING UP THE REDIRECT FOR YOUR CAMPAIGN
Seeing as osCommerce 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 = 'yourdomain.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 FOR OSCOMMERCE
Download tradetracker.php and log in to the FTP account of your osCommerce based shop.

Upload tradetracker.php to the /includes/ folder of your web server. DO NOT MODIFY THE FILE.

Navigate to the root of your web server and locate, open/edit or download/edit the file checkout_success.php

Copy this code above the div class="contentText" in the checkout_success.php file.
<?php
$campaignID = '[marker]CAMPAIGN_ID[/marker]';
$productID = '[marker]PRODUCT_ID[/marker]';
$imageTag = include './includes/tradetracker.php';
echo $imageTag;
?>

The code must be placed above the div class="contentText", like:
<!-- code above goes here -->
<div class="contentText">

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]=16
05-Dec-2014 09:17:49
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 15:52:28
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 15:47:08
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 12:51:12
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 15:48:17
merchant ePages 6 and higher Standard implementation ePages 6 TRADETRACKER CONVERSION IMPLEMENTATION

The ePages webshop system uses the StratoShop backend code.

You can use the instructions for StratoShop to complete your implementation.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=30
01-Jul-2014 14:25:44
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



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 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 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 15:56:18
merchant General All General conversion script GENERAL TRADETRACKER CONVERSION SCRIPTS Click here in case you need to use a MULTI COUNTRY SOLUTION with a TRACKING GROUP ID

Here you will find our general conversion scripts that can be used to place on the order confirmation page or thank you page of your site.
To register conversions, the script must be populated with information from your site.

SALES CONVERSION SCRIPT EXAMPLE

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


LEAD CONVERSION SCRIPT EXAMPLE

<script type="text/javascript">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'lead',
campaignID: '[marker]CAMPAIGN_ID[/marker]',
productID: '[marker]PRODUCT_ID[/marker]',
transactionID: '[marker]{transactionID}[/marker]',
descrMerchant: '[marker][/marker]',
descrAffiliate: '[marker][/marker]'
});
</script>
<noscript>
<img src="//tl.tradetracker.net/?cid=[marker]CAMPAIGN_ID[/marker]&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.
vcTextual stringDISCOUNT50NoVoucher code variable. The voucher code is a variable value that is used on checkout page of your web shop.

SETTING UP THE REDIRECT INSTRUCTIONS
IMPLEMENTATION CONSIDERATIONS
PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=27
07-Jun-2019 15:28:45
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 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]&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]&amp;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]&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.
vcTextual stringWelcome-123No The (main) discount code used for the order in question. Used in case you would like to work with unique voucher codes for certain publishers
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=29
08-Dec-2020 10:50:12
merchant General All 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:

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