|
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]&pid=[marker]PRODUCT_ID[/marker]&tid={$sOrderNumber}&tam={$sBasketItem.amount}&data=&qty=1&descrMerchant={$sBasketItem.articlename}&descrAffiliate={$sBasketItem.articlename}&event=sales&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]&pid=[marker]PRODUCT_ID[/marker]&tid={$sOrderNumber}&tam={$sBasketItem.amount}&data=&qty=1&descrMerchant={$sBasketItem.articlename}&descrAffiliate={$sBasketItem.articlename}&event=sales&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
|
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
|
4
|
Standard implementation
|
 XT:COMMERCE 4 VEYTON TRADETRACKER CONVERSION IMPLEMENTATION
SETTING UP THE REDIRECT
Seeing as XT:Commerce uses php you can download the redirect file here download index.php After downloading, please add your domainName to line 6.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines. When the redirect is working, follow the instruction for setting up the conversion registration below.
Log in to your FTP account and open and edit the file xtCore/pages/page_action/checkout.success.php
At the bottom of the file you will find a php closing tag ( ?> ) above this closing tag the code that is found here must be added:
// TradeTracker conversion script
$campaignID = '[marker]CAMPAIGN_ID[/marker]';
$productID = '[marker]PRODUCT_ID[/marker]';
$orderID = !empty($success_order->oID) ? htmlspecialchars($success_order->oID) : '';
$orderAmount = empty($success_order->order_total['total']['plain']) ? 0.00 : (float) $success_order->order_total['total']['plain'] / 1.2; // The 1.2 is your VAT ratio.
$trackingCode = "<script type=\"text/javascript\">
var ttConversionOptions = ttConversionOptions || [];
ttConversionOptions.push({
type: 'sales',
campaignID: '$campaignID',
productID: '$productID',
transactionID: '$orderID',
transactionAmount: '$orderAmount',
quantity: '1',
descrMerchant: '$descrMerchant',
descrAffiliate: '',
currency: '',
trackingGroupID: '[marker][/marker]'
});
</script>
<noscript>
<img src=\"//ts.tradetracker.net/?cid=$campaignID&pid=$productID&tid=$orderID&tam=$orderAmount&qty=1&event=sales\" alt=\"\" />
</noscript>
<script type=\"text/javascript\">
(function(ttConversionOptions) {
var campaignID = 'campaignID' in ttConversionOptions ? ttConversionOptions.campaignID : ('length' in ttConversionOptions && ttConversionOptions.length ? ttConversionOptions[0].campaignID : null);
var tt = document.createElement('script'); tt.type = 'text/javascript'; tt.async = true; tt.src = '//tm.tradetracker.net/conversion?s=' + encodeURIComponent(campaignID) + '&t=m';
var s = document.getElementsByTagName('script'); s = s[s.length - 1]; s.parentNode.insertBefore(tt, s);
})(ttConversionOptions);
</script>";
define('TRADETRACKER_TRACKING_CODE', $trackingCode);
Save and/or upload the file to your server.
Navigate to: /templates/YOUR_THEME_SKIN_DIRECTORY/xtCore/pages/checkout/subpage_success.html
Open and edit the file subpage_success.html and at the top of this file add
{txt key=TRADETRACKER_TRACKING_CODE}
Save and/or upload the file to your server.
If your redirect is working the implementation can be tested.
Please keep in mind that although we do our very best to cover a wide variety of different implementations and web shop systems, programming languages and conversion registration methods for different situations, we want to state here that they are all merely examples and are not guaranteed to work for your specific situation or specific conversion or tracking needs. The reason for this is that the implementation descriptions provided are based on default system configurations and do not take system configuration settings, customisations and usage of plug-ins into account. Besides that there are also a lot of other variables that can have impact on the correct working of our tracking and conversion registration which we just can't know upfront. In case you do encounter or experience issues when implementing our tracking, please report this to your account manager and describe (in detail) the steps you took and if it's possible, provide the code and/or files you are using for your implementation to the account manager.
Shortlink to this article: https://sc.tradetracker.net/implementation/overview?f[id]=39
|
14-Mar-2019 15:52:04 |
|
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]&pid=[marker]PRODUCT_ID[/marker]&tid={$Bestellung->cBestellNr}&tam={$Bestellung->WarensummeLocalized[1]}&data=&qty=1&descrMerchant={$Bestellung->cZahlungsartName}&descrAffiliate=&event=sales&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
|
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
|
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
|
VirtueMart (Joomla)
|
2.0.0 and higher
|
Standard implementation
|
 VIRTUEMART 2.0.0 AND HIGHER (JOOMLA) TRADETRACKER CONVERSION IMPLEMENTATION
Seeing as Virtuemart (Joomla) uses php 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 a folder in the root of your website. The folder must be named a word that best represents your webshop's content.
For more information regarding setting up the redirect we refer you to setting up the redirect guidelines.
VIRTUEMART CONVERSION IMPLEMENTATION
We have created a general TradeTracker conversion handler file for Virtuemart 2.0.0 and higher (Joomla) that also must be placed on your server.
Download: tradetracker.php No modifications must be made to this file.
Upload tradetracker.php to your server in folder /components/com_virtuemart/views/cart/tmpl/
After that open and edit the order_done.php file (also located in /components/com_virtuemart/views/cart/tmpl/ )
Within the order_done.php file locate the following line of code:
[marker]echo $this->html;[/marker]
Below that line copy and paste the following code:
$tt_campaignID = '[marker]CAMPAIGN_ID[/marker]';
$tt_productID = '[marker]PRODUCT_ID[/marker]';
$tt_trackingGroupID = '[marker][/marker]';
$tt_scriptTag = include_once 'tradetracker.php';
echo $tt_scriptTag;
After these steps are executed, 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]=28
|
12-Dec-2014 14:28:51 |
|
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
|
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
|
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 |
