 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 |
