Target group Name Version Version info Implementation steps Last modified
merchant Magento Plugin 1.x - 2.x MAGENTO CONVERSION IMPLEMENTATION

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

Magento version 2

Magento version 1 by third party Magmodules.eu.
For support, please refer to Magmodules in case you might run into configuration issues. Their professional support has short response times.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=70
15-Dec-2021 16:39:24
merchant 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 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
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 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 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 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 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 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 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