Setting up Parallel Tracking with Tradedoubler.
With parallel tracking users are able to transition between pages quicker which can reduce lost visits. Faster load times can lead to increased conversion rates, and have positive impact on your revenue. With parallel tracking end user is sent directly to the advertisment destination page while click measurement, which usually is a part of a redirection, happens in the background. It's used in Google Search, Shopping, Display and Video campaigns.
To learn more about Google Parallel Tracking visit https://support.google.com/google-ads/answer/7544674
Do not have a publisher account? Register with Tradedoubler and get started today!
To obtain the correct landing page URL, please click through your Tradedoubler affiliate link. Once on the advertiser's landing page, copy the URL from the address bar, ensuring that all necessary additional parameters are present. For example:
https://www.advertiser.com/destination_page?utm_source=Tradedoubler&utm_campaign=affiliate&foo=bar&tduid=d7e37510b0db1ee3aff3b38d6d7bd373&tdpeh=18dv%2AkvqM%2AEu9vtQDVHuHylsRUlBhBBHsOW_1Dn6YjpUooWqDkJMdzN
Please make sure to delete “tduid” and/or “tdpeh” parameters if present.
https://www.advertiser.com/destination_page?utm_source=Tradedoubler&utm_campaign=affiliate&foo=bar
To guarantee correct tracking by Tradedoubler, please set the "Final URL suffix" to: tduid={gclid}_deviceid. Correctly prepared Final URL example:
https://www.advertiser.com/destination_page?utm_source=Tradedoubler&utm_campaign=affiliate&foo=bar&tduid={gclid}_deviceid
This URL will be called asynchronously, "in the background" remaining invisible to the end user. It is not the user destination! To guarantee correct tracking by Tradedoubler please append two extra parameters to your Tradedoubler tracking link:
Name | Value |
---|---|
deviceId | {gclid}_deviceid |
f | 0 |
Correctly prepared Tracking Template URL examples:
https://clk.tradedoubler.com/click?p=123&a=234&g=345&f=0&deviceid={gclid}_deviceid
https://clk.tradedoubler.com/click?p(123)a(234)g(345)f(0)deviceid({gclid}_deviceid)