HOW TO INTEGRATE TRACKING

SERVER-TO-SERVER CONVERSION TRACKING

BitTorrent server-to-server conversion tracking is designed to facilitate persistent tracking between BitTorrent’s ad network and our advertisers. This tracking method will not use cookies to store information, but instead utilize a tracking server to store a unique identifier that will communicate to the advertiser tracking server when a user has completed a conversion (also known as a server postback). BitTorrent’s server-to-server tracking has the benefit of supporting real-time conversion events for optimization of advertiser campaigns via our ad server, as well as providing advertisers with the benefit of identifying acquired users for cohort analyses, publisher source quality, and LTV monetization.

Server-to-server conversion tracking can be used for web-based campaigns trafficked through the Leaderboard or MREC placements.

 

How it works
When a user clicks on an ad, a dynamically generated transactionid is appended to the landing page url. The TRANactionid is passed in through thSACTIONID is a dynamic value consisting of 32 characters. This value is alphanumeric and includes the symbols + and _. This transe tracking URL given to BitTorrent by the advertiser. On successful conversion, your servers should ping BitTorrent’s servers via the callback URL, including the partnerid and transactionid value that was passed in on the ad click. This event should happen in real-time in order to optimize the campaign performance.

 

BitTorrent Callback URL

BitTorrent’s callback URL in its most basic form is as follows:
http://events.bittorrent.com/partner?partner=[PARTNER_ID]&id=[TRANSACTIONID_GOES_HERE]
Your dedicated Account Manager will provide you with your Partner ID, a static value, during campaign onboarding. The &id parameter is the dynamic transactionid value that BitTorrent’s ad server will pass to you.

 

Advertiser Tracking Links

You must provide a tracking link to BitTorrent that includes a parameter where the specified transactionid dynamic value can be passed in. This URL must be able to accept the transactionid (32 characters) as a value pair.

For example, if your tracking link is: www.domain.com/campaign1 and the parameter where a dynamic value can be passed in is called subid, your tracking link becomes http://www.domain.com/campaign1?subid=[TRANSACTIONID_GOES_HERE]

example:
http://domain.com/campaign1 becomes http://domain.com/campaign1?subid=1234567890
On the advertiser’s end, the tracking link parameter must be mapped to the BitTorrent callback URL’s &id= parameter. In the aforementioned example, the “&subid” value from the tracking link must be set to the “&id=” value in the BitTorrent callback URL.

 

SERVER-TO-SERVER CONVERSION TRACKING WITH PAYOUT DATA

 When user clicks on an ad, a dynamically generated transactionid is appended to the landing page, along with a unique lineitemID. The advertiser must provide BitTorrent with a landing page url that can accept the transactionid (32 characters) as a value pair as well as the lineitemID (6-12chars). example:
http://domain.com becomes http://domain.com?subid=1234567890&lineitemID=2341245
When the user converts, a message must be sent back to BitTorrent appending the provided partnerid, the dynamically generated transactionid, lineitemID and the amount of revenue generated by BitTorrent.
example:
http://events.bittorrent.com/partner?partner=%PARTNER_ID%&id=%TRANSACTIONID_GOES_HERE%&lineitemID=%LINEITEM_ID%&payin=%REVENUE% becomes
http://events.bittorrent.com/partner?partner=yourpartnername&id=1234567890&lineitemID=234156&payin=1.60

 

IMPLEMENTING THE ADZERK COOKIE-BASED PIXEL CONVERSION

 For CPA campaigns, we can use standard cookie-based conversion tracking to fire off a conversion event. This pixel should be implemented in the head element of the conversion event page. Using a standard conversion pixel, a cookie will be placed on the user’s default browser upon clicking the ad. When a user reaches the conversion event, the pixel code is loaded and BitTorrent’s ad server records the conversion event.

Directions:

1. Place the Adzerk conversion pixel code in the head element of the page where the conversion event is completed (typically the registration confirmation or success page)
• If the pixel code can’t be placed in the head element, please place it in the body of the conversion page as close to the top as possible
2. Once the Adzerk conversion pixel is successfully added to the conversion event page, please let your Account Manager know and they will coordinate a conversion test to validate tracking

JavaScript Based Conversion Pixel

example pixel code:
<html>
   <head>
         <script type=”text/JavaScript”>
         var it=document.createElement(“img”);
         var u=”https://engine.ap.bittorrent.com/e/5682/29668/e.gif”;
         var t=new Date().getTime();
         var ut=u+”?_=”+t;
         it.src=ut”
         it.border=0;
         </script>

   </head>
<body>
This a Conversion Event Page.
</body>
</html>
*pixel code appears in purple

Image-Based Conversion Pixel

example pixel code:
<html>
    <head>
          <!-- /* Adzerk Image Conversion Tag */ -->
          <div id=’cvid_29668’ style=‘position: absolute; left: 0px; top: 0px; visibility: hidden;’>
          <img src= ‘http://engine.ap.bittorrent.com/e/5682/29668/e.gif?t=%%RANDOM%%’
          width=’0’ height=’0’ alt= ‘ ‘ />
          </div>
          <!-- end generated tag -->

    </head>
   <body>
        This a Conversion Event Page.
   </body>
</html>

*pixel code appears in purple

Last Updated: Jul 06, 2015 03:46PM PDT

Need a Human?

Contact BitMedia Support