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
|
General
|
All
|
Multi country campaign conversion script
|
MULTI COUNTRY CAMPAIGN CONVERSION SCRIPTS TradeTracker campaigns get a unique campaign ID per country in which the campaign will be active. The Tracking Group ID is used to be able to use just 1 general conversion script on your confirmation page, instead of a script for each country in which the campaign is active. The way that this works is that our system will check for each campaign within the tracking group where the originating click came from and assigns any resulting conversions to the correct campaign in the correct country.
The multi-country conversion script should only be used after receiving a Tracking Group ID from your account manager.
Please note that the script you choose below must contain 1 of your campaign ID's (in general just the main campaign ID) in order for the conversion scripts to work.
The campaign ID that is added is only used to check if the main campaign is active, the tracking group number is used to assign the conversion to the correct campaign in our system.
MULTI COUNTRY CAMPAIGN SALES CONVERSION SCRIPT
<script type="text/javascript"> var ttConversionOptions = ttConversionOptions || []; ttConversionOptions.push({ type: 'sales', campaignID: '[marker]CAMPAIGN_ID[/marker]', productID: '[marker]PRODUCT_ID[/marker]', transactionID: '[marker]ORDER_ID[/marker]', transactionAmount: '[marker]ORDER_AMOUNT[/marker]', quantity: '1', descrMerchant: '', descrAffiliate: '', currency: '', vc:'', trackingGroupID: '[marker][/marker]' }); </script> <noscript> <img src="//ts.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&tam=[marker]ORDER_AMOUNT[/marker]&data=&qty=1&descrMerchant=&descrAffiliate=&event=sales&currency=[marker]EUR[/marker]&vc=" alt="" /> </noscript> <script type="text/javascript"> // No editing needed below this line. (function(ttConversionOptions) { var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null); var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m'; var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s); })(ttConversionOptions); </script>
MULTI COUNTRY CAMPAIGN LEADS CONVERSION SCRIPT
<script type="text/javascript"> var ttConversionOptions = ttConversionOptions || []; ttConversionOptions.push({ type: 'lead', campaignID: '[marker]CAMPAIGN_ID[/marker]', productID: '[marker]PRODUCT_ID[/marker]', transactionID: '[marker]ORDER_ID[/marker]', descrMerchant: '', descrAffiliate: '', trackingGroupID: '[marker][/marker]' }); </script> <noscript> <img src="//tl.tradetracker.net/?tgi=[marker][/marker]&pid=[marker]PRODUCT_ID[/marker]&tid=[marker]ORDER_ID[/marker]&data=&descrMerchant=&descrAffiliate=&event=lead" alt="" /> </noscript> <script type="text/javascript"> // No editing needed below this line. (function(ttConversionOptions) { var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null); var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m'; var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s); })(ttConversionOptions); </script> OUR UNIVERSAL CONVERSION SCRIPTS PRE-CONFIGURED WEB SHOP CONVERSION IMPLEMENTATION SOLUTIONS SETTING UP THE REDIRECT INSTRUCTIONS IMPLEMENTATION CONSIDERATIONS
VARIABLES OVERVIEW AND DESCRIPTIONS
Available variables | Possible value(s) | Example | Required | Description |
type | sales or lead | sales | Yes | Define if the conversion is a sale or a lead. |
campaignID | Numeric string | 1234 | Yes | Your campaign ID.The campaign ID as provided by TradeTracker. |
productID | Numeric string | 4321 | Yes | Your product ID. The product ID as provided by TradeTracker. |
transactionID | Textual string | ABC-12345 | Yes | Your shop's internal and unique order identifier. The transaction identifier (e.g. orderID) is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. |
transactionAmount | Numeric string | 123.45 | Yes, if type is 'sales'. | Transaction amount variable. The transaction amount is a variable value that is available on the order confirmation page of your web shop. The variable used is different for each shop or custom solution. In case of a lead campaign this can be left blank or set to '0'. |
quantity | Numeric string | 1 | No | Intended for statistical analysis in future software releases. You are able to specify the quantity of the order here. Currently this does not affect the registration of the order, in the future this will be used to be able to calculate the order amount for example (if this has added value for you) and it will be used for statistical information. |
descrMerchant | Textual string | Samsung UE55HU7500 | Yes | Detailed description of the order. Used for statistical purposes. Visible for the merchant only. You can add variable values here and/or other order information you might want to see in your TradeTracker account. Use this to add product information or order information. |
descrAffiliate | Textual string | Samsung Ultra HD TV | Yes | Description of the order. Visible for affiliates only. Used by affiliates for campaign optimisation. |
currency | Textual string | USD | No | Currency of the transaction. ISO 4217 standard, e.g. EUR, USD, GBP, PLN etc. Defaults to company currency if left empty. Also used in combination with our automatic currency conversion option This option is turned off by default. Ask your account manager if you need this option to be activated. |
trackingGroupID | Numeric string | 11 | Leave blank by default unless instructed to do otherwise by TradeTracker | Used to group campaigns for multiple countries. |
vc | Textual string | Welcome-123 | No | The (main) discount code used for the order in question. Used in case you would like to work with unique voucher codes for certain publishers |
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=29
|
08-Dec-2020 10:50:12 |
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¤cy=#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
|
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
|
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]&pid=[marker]PRODUCT_ID[/marker]&tid=[{$order->oxorder__oxordernr->value }]&tam=[{ $order->getTotalOrderSum() }]&data=&qty=1&descrMerchant=[{ $oxcmp_user->oxuser__oxcustnr->value }]&descrAffiliate=&event=sales&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
|
xt:Commerce
|
3
|
Overview
|
XT:COMMERCE 3 TRADETRACKER CONVERSION IMPLEMENTATION
SETTING UP THE REDIRECT Seeing as XT:Commerce uses php you can download the redirect file here download index.php After downloading, please add your domainName to line 6.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines. When the redirect is working, follow the instruction for setting up the conversion registration below.
We have created a general TradeTracker conversion handler file for xt:Commerce 3 that must be placed on your server. No modifications must be made to this file.
Download the tradetracker.php file for xt:Commerce here
Log in to your FTP account and upload the tradetracker.php file to the /includes/ folder of your xt:Commerce installment.
Open and edit the file checkout_success.php that is located in the root of your XT:Commerce installation. Within checkout_success.php locate the following line of code:
$main_content = $smarty->fetch(CURRENT_TEMPLATE.'/module/checkout_success.html'); ABOVE this line place the following code:
// Begin Tradetracker xt:Commerce 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); // End TradeTracker xt:Commerce code Save and/or upload the file to your server.
Locate your checkout_success.html template file. This file is part of the theme your are using. and normally would be found at the following location:
/templates/{TEMPLATE_NAME}/module/checkout_success.html
Open and edit the file checkout_success.html and at the bottom of this file add the following code:
<!-- TradeTracker conversion tracking start --> {$tt_imageTag} <!-- TradeTracker conversion tracking end --> Save and/or upload the file to your server.
If your redirect is working the implementation can be tested.
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=14
|
28-Jan-2016 14:51:14 |
merchant
|
General
|
All
|
Redirect
|
IMPLEMENTING TRADETRACKER REDIRECT AND CONVERSION INSTRUCTIONS AND CONSIDERATIONS The articles on these pages are created to help you implement our tracking and conversion registration method.
If you arrived at this portal by using a link that was sent to you, we would like to inform you about the accompanying document to these pages. This document contains more or less similar information as to be found on this site, but is structured chronological and contains links to the relevant pages on this site, making it somewhat easier to read, depending on what you prefer. The document is part of the start mail you received or available in your account.
Implementing our click registration and conversion tracking should take about 30 minutes up to 2 hours for general situations. Although it can be done in 15 minutes in case you are already familiar with setting it up using an available pre-configured implementation method and if there are no unexpected surprises. It can however be longer in more complex set-ups with more stakeholders or when encountering other problems.
We highly recommend you to read the information in the document or on this site. These articles contain important information about how, why and what you should do in order to set up your campaign successfully.
Setting up the TradeTracker tracking consists of 2 parts: 1) Registering a click from the affiliate’s website to your site. 2) Registering resulting conversions to be able to match the click to the sale.
In order to be able to implement our tracking system, you must be able to: 1) Create a redirect location on your (sub) domain. 2) Make modifications to the checkout success / order confirmation page of your web shop system.
The first thing that needs to be done is getting the click registration mechanism to work. The redirect is based on creating a location on your domain which will handle all incoming clicks from your affiliates. This can be done by either creating a separate rewrite path or physical directory and making one of our redirect example code files available to handle the incoming clicks. Optionally, you may also create a subdomain (e.g. offers.merchant.com) and making the desired redirect available within the root of your subdomain. This is the preferable method in case you want to keep this implementation separate from your regular developments on your main domain.
The available languages we offer are ASP (.asp) | Coldfusion (.cfm) | CSHARP (.aspx) | JSP (.jsp) | PERL (.pl) | PHP (.php) | Python (.py) | Visual Basic ASPX (.aspx).
DOWNLOAD THE AVAILABLE REDIRECT REDIRECT SCRIPT EXAMPLES HERE and extract the zip-file to your computer.
The zipped file contains directorys that represent the programming language of the redirect script example. You should choose an redirect script example in a language (extension) that is supported by your server.
ADD YOUR DOMAIN NAME TO THE INDEX REDIRECT FILE The redirect script example to use depends on the type of server and the programming language that is supported by your server. To make sure our tracking is working as intended, the domain of your website (without www. ) must be added to the redirect file. Check the file for the "domainName" variable and change to your main domain accordingly. If your shop is running on www.merchant.com or shop.merchant.com for example, the domainName value to enter would be "merchant.com".
By default the redirect script example we provide should work in most situations. They are created, tested and verified to work for the majority of our clients. We do not encourage further modification of the provided redirect script example, unless you have a very good reason to do so and know exactly what you are doing.
MAKING THE REDIRECT AVAILABLE Within the introduction e-mail that you received from your account manager a suggestion for the location of the redirect location is made. If you decide to use an other location, please communicate this to your account manager because the correct location is needed to get your campaign to work as intended.
CHOOSING A LOCATION FOR THE REDIRECT The redirect location name should be a phrase that best represents your shop or topic of your site. If you have a website that sells fashion items or clothing, the name of the redirect directory should represent this. For instance in this case it might be www.yourwebsite.com/fashion/ or www.yourwebsite.com/clothing/.
Please refrain from using a name that resembles any connection or relation to TradeTracker like www.yourwebsite.com/tt/ www.yourwebsite.com/tracking/ www.yourwebsite.com/tradetracker/ or www.yourwebsite.com/redirect/ for example.
You should verify that the suggested directory is not already part of your website’s link structure. This can be the case if URL rewriting is used for the suggested directory and content is already attached to the suggested location. If that is the case, please think of an alternative location/directory to place the redirect file.
Turn URL rewriting off in case you use an actual "physical" directory In case your site is using URL rewriting to create pretty links on your website, URL rewriting must be turned off for the redirect directory in order for it to work correctly. This is done in different ways for different server environments. On an Apache web server, the URL rewrite engine can be turned off for a specific directory by placing an .htaccess file within the redirect directory containing the line:
RewriteEngine Off For more information about URL rewriting and links to different server settings we refer you to Wikipedia - URL Rewrite Engine.
In case your server supports .htaccess files you can download a zipped .htaccess file to use here.
SUMMARY TO SET UP THE REDIRECT LOCATION
1. Determine the server environment and choose the programming language format accordingly (or create one based on one of the example codes) 2. Create the redirect location (either a rewrite, physical directory or subdomain) 3. Set the domainName variable with your main domain (without www.) in the redirect script example 4. Make the redirect script publicly available at the chosen location and if using an actual physical directory, turn off the URL rewrite engine according to your server configuration options 5. Use the tracking test URL that corresponds to the redirect location to test the redirect
When these steps are done, you are ready to test the redirect to your site by using the tracking test link.
If you did not receive the tracking test link or used a different then suggested redirect location, please contact your account manager.
SETTING UP THE TRADETRACKER CONVERSION SCRIPT AND IMPLEMENTATION CONSIDERATIONS Before you start copying and pasting the codes that can be found by clicking the links below to your site and come to the conclusion that it's not working as you had planned, please hold on to your horses. Implementing our conversion script requires some thought and consideration. The reason for this is that there are a lot of options and configuration situations to take into account.
Do you have a custom built website? If so, what program language is used? Do you use a Payment Service Provider? An existing web shop system? Are for example things that influence the technical implementation strategy to follow.
We have described a couple of things for you to consider or determine before continuing the implementation.
When you have a clear picture of your technical environment and the other factors described above, you have to main options:
PRE-CONFIGURED WEBSHOP CONVERSION IMPLEMENTATION SOLUTIONS click the link above to see if we have a solution for your environment available. The advantages are that these solutions are already configured to use the correct variable values and tested in a default installation of the web shop system.
OUR UNIVERSAL CONVERSION SCRIPTS. Our universal script is the script that we use to create the web shop specific solutions. The script requires the variable values that are needed to register conversions within our system to be added manually, but it can be used for any situation. It does require some basic programming knowledge of the environment in which the script must be placed or use the supported variable placeholders of your shop or environment.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=1
|
30-Jul-2020 14:01:11 |
merchant
|
General
|
All
|
Server to Server (S2S) tracking
|
Setting up Server to Server (S2S) tracking Server to server tracking is used in situations where regular conversion registration is not possible by means of placing our tracking code within the publicly available pages on your website (known as "client-side tracking"). The S2S method relies on a unique click identifier to be stored on your server and passed back at the time of the conversion.
We are able to pass our unique click identifier to each page on your website and you are free to choose exactly what the name of this parameter should be, e.g. "someparameter".
The tracking data value is a unique reference to identify clicks within our system and is unique for each incoming click on your website.
As a result, a link to one of your landing pages will look something like:
http://yourwebsite.com/landing/page?someparameter=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker] Please note we always send this parameter url-encoded. Also, it's important this value is stored somewhere within a storage of choice, e.g. a memory database and/or a relational database, depending on the usage. When using a database, it can for example be stored within a column ttClickID or any other column name you prefer.
How to pass back the click identifier Whenever a conversion is triggered for which an affiliate should receive a reward, this click identifier should be passed back to TradeTracker. One of the tasks that lies ahead for your development team, is to store this unique click identifier, together with the information that is used to trigger this conversion.
Example Let's assume you run an online gaming website and you reward affiliates for bringing in new players. It's important that our unique click identifier is stored together with the new player information so that it can be accessed at the time of conversion trigger.
Within a database it would look something like:
id | name | user | eml | regdate | ttClickID |
111 | J. Smith | jsmith00 | jsmith@eml.net | 2014-09-01 | [marker]0::12345::abc::::1405418672[/marker] |
112 | J. Doe | player123 | doe.j@email.org | 2014-09-02 | 12::54321::def::::1405419867 |
LEAD CONVERSION CALLBACK In case an event is triggered that resembles a lead conversion (e.g. user registration), the following callback format is used:
https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}&data=[marker]{ttClickID}[/marker]&vc={voucherCode}
SALES CONVERSION CALLBACK If an event is triggered that resembles a sales conversion (purchase, booking), the following callback format is used:
https://ts.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid={transactionID}&tam={transactionAmount}&descrMerchant={descrMerchant}&descrAffiliate={descrAffiliate}¤cy={currency}&data=[marker]{ttClickID}[/marker]&vc={voucherCode} In the above callbacks the {ttClickID} is tied to a fixed "data" parameter and its value must be replaced by the value saved during the initial click (and eventually stored within a database, like the table above).
Note: Please make sure all values are URL-encoded.
Example formatted callback
https://tl.tradetracker.net/?s2s=1&cid=[marker]CAMPAIGN_ID[/marker]&pid=[marker]PRODUCT_ID[/marker]&tgi=&tid=123456&descrMerchant=new%20player&descrAffiliate=new%20player&data=[marker]0%3A%3A12345%3A%3Areference%3A%3A%3A%3A1405418672[/marker]
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=31
|
30-Nov-2021 17:07:39 |
merchant
|
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¤cy=#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
|
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&tgi=&pid=PRODUCT_ID&tid={{ order.order_number }}&tam={{ line_item.price - line_item.line_level_total_discount | divided_by: 100 }}&data=&qty={{ line_item.quantity }}&descrMerchant={{ line_item.sku }}&descrAffiliate=&event=sales&currency={{ checkout.currency }}&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 |