In order to ensure you track successfully with Bucksense, we must have the ability to know and attribute a conversion that was generated as a result of the traffic sent to your website or app.
There are two main implementation tracking: Pixel based tracking and Server to Server Postback tracking.

If you want to track click and conversions even in a 3rd party tracking tool, you need to know if this supports Pixel or Postback tracking.

Find below a sample list of most used ad servers and the related supported tracking:
Google Analytics (Only pixel)
Omniture (Pixel)
Appsflyer (Postback)
Hasoffers (Postback)
Voluum (Postback)

Pixel based tracking

Bucksense’s Advanced Tracking capabilities are designed to provide multiple key data points of the traffic driven to the Advertiser’s offers.
To do so, it is essential that Bucksense Pixel is implemented in Advertiser System or site to notify us when conversions occur and let us gather meaningful post-click information, for example user’s device or OS.
Bucksense supports two kinds of pixel-based tracking methods: iFrame and Image pixels.
In both methods, you can choose between the following attribution methods:

A) Using Bucksense Transaction ID (cookie less tracking)
This method requires the use of a tracking tool.
If you would like to go ‘cookieless’ tracking, your tracking system will need to have the ability to receive and pass back the Bucksense Transaction ID at the time of making the conversion, call to the Bucksense platform.
The Bucksense Transaction ID can be passed to the URL defined in a Bucksense offer, in any parameter you require, with the macro {transaction_id}.

B) Tracking through cookies
If you choose to use the attribution through cookies, then there is nothing you will need to implement as we will directly read our cookie for attribution purposes.
This cookie contains all the session info for that user, and on conversion the offer pixel will pull this session info from the user’s browser to authenticate they came from a tracking link.
If everything checks out, the conversion is created and showed in the Bucksense real time reports.

How to get the Pixel in Bucksense console

Bucksense provides you the pixel that needs to be implemented in the “thank you” page or the page that you consider a “conversion” for your campaign.
The Pixel needs to be implemented in the </body> tag of the HTML code.
If you don’t have access to the page, you need to contact your webmaster.

Follow these steps to get the pixel in Bucksense console:

  1. Click on Offers/Campaigns> Offer List in the Navigation Bar and select the offer for which you will be setting up the Conversion Tracking
  2. Once you had filled in the basic information (Offer name, Landing page URL etc).
    Select HTTP/HTTPS Image pixel or HTTP/HTTPS iFrame pixel in the Conversion Tracking Method drop down menu, depending on the protocol you are using in the landing page (i.e if the landing page is HTTPS, use HTTPS Pixel) and click on Save.
  3. Access the Advanced Tracking section, click on Conversion Tracking, then click on Open Conversion Tracking button

    Select the attribution method (cookie less or through cookie) you want to use in the Generated Conversion Tracking Url,

  4. Copy the generated URL and set it in your “conversion page”.
    If you want to track multiple post conversion events and to create custom events see here

Server to server Postback tracking

If your adserver supports Server to server Postback tracking, then the first step is to integrate our postback.
Postback tracking is more accurate than pixel, since there is a direct connection between the two servers.
Moreover it provides you with useful additional info like: OS, Carrier, Publisher, Exchange, etc

If you choose to implement a Server to Server Post Back, your tracking system must have the ability to receive the Bucksense Transaction ID which is an integer that can be passed in any parameter you require.
We pass this value with the macro {transaction_id}.

Bucksense Postback is the following:{param1}

This URL needs to be integrated in your tracking tool.
Replace the {param1} with the parameter your tracking tool uses to track conversions.

Example: If your tracking tool uses ClickID, the Postback would be integrated like this:{ClickID}


How to create a S2S Postback tracking in Bucksense console

Follow these steps to create a Server to Server Postback tracking in Bucksense Console:

  1. Click on Offers/Campaigns> Offer List in the Navigation Bar and select the offer for which you will be setting up the Conversion Tracking
  2. Once you have entered your Landing page URL (example:, you need to add the parameter your tracking tool uses for tracking conversions to your URL (in the sample above ClickID):
  3. Then add the macro which Bucksense uses to track conversions: {transaction_id}.
    You can do this manually or by clicking on the Click ID macro in the macros field.

    Final Landing Page URL will be looking like the following:{transaction_id}

  4. Select HTTP/HTTPS Server postback w/Transaction ID in the Conversion Tracking Method drop down menu, based on the protocol you are using in the landing page (i.e if the landing page is HTTPS, use HTTPS Server Postback) and click on Save.

    If you want to set more macros besides conversions, click in the “Landing page URL” box and you will see all the macros available.
    Additional Macros can be added, into the Landing page URL field, so, every time an user clicks on your ad, our server replaces the macro with dynamic informations about the click, before redirect the user to the Landing Page URL.


How to test the conversion tracking (both: S2S Postback and Pixel)

To test a conversion and see if the connection between the two servers has been done successfully, use this link:

Replace yourOfferID with the ID of the offer you are testing in Bucksense, then click the test link with a device, access the Landing Page URL and generate a conversion.
Contact your AM to see if the conversion has been fired successfully.