Implementation

Step 1

· The visitor arrives at the Kelkoo website.

· The user carries out a search and your offers are displayed.

Step 2

· The visitor clicks on your ad and is redirected to the TradeDoubler server where a persistent cookie called "TRADEDOUBLER" is placed on the user's browser. This cookie contains the TDUID (set in the TradeDoubler database - unique per visitor) and provides information about the click.

Step 3

· The visitor is then sent to your redirect page, while TradeDoubler sends the TDUID value and URL as parameters in the URL.

Step 4

· The redirect page forwards the user to the appropriate page on the advertiser's website. This is usually the product page you have specified in your product feed to Kelkoo.

· The URL parameter is checked and the user is forwarded on to the correct redirect page.

· The TDUID that is sent by TradeDoubler to your redirect page is picked up and stored in two different ways:

  • - In a persistent cookie called TRADEDOUBLER set by your domain on the visitor's computer
  •  
  • - As a session variable The codes in the example code appendix must be implemented in a file hosted on your web-server, usually called something like http://www.your-site.com/redirect.asp. Please send us the exact URL location of your redirect page so that we can update our system to redirect all traffic to that page.

 

Step 5

· The user is forwarded to the checkout and completes their transaction.

Step 6

· The TAG must only be implemented on your confirmation or "thankyou" page. The TAG is an invisible 1x1 image which provides information on the click and is hosted by TradeDoubler. This TAG is called from different sub-domains, depending on the type of the event: · All sales TAGs are called on tbs.tradedoubler.com ("s" for sale) · All leads TAGs are called on tbl.tradedoubler.com ("l" for lead) Some parameters must be sent back to TradeDoubler with the tracking pixel request. Note the difference between sale and lead parameters below in this document.

Step 7

· The TradeDoubler tracking server attempts to retrieve information from the cookie on the user's browser, set in step 2 TradeDoubler validate the lead/sale upon the TAG request and can only validate the lead/sale if the visitor has a TDUID or TradeDoubler cookie for that program. Sale TAG example: Lead TAG example: Your account manager will send you your unique organisation and event IDs.