In order to ensure you track successfully with Bucksense, Bucksense 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.

Conversion events vary by business but usually are one of the following:

  • Lead
  • Sale
  • Subscription
  • Email opt-in
  • Installation
  • In-app purchase

There are two main implementation cases: Global Pixel without cookies and Offer Based Pixel with cookies and without cookies

Global Pixel without cookies

With a global pixel, if it is supported by the 3rd party tracking platform you use or your own tracking system, you have the ability to set up the Bucksense tracking system only once.
That way, any offer that you would like to have promoted within Bucksense will not need to have a separate conversion tracking implementation.

To setup the Global Pixel code, you have the following options:

Server to Server Post Back

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}.
You must ensure that all of the URLs that you define within your offers in the Bucksense platform include this macro.

The URL to insert in your tracking platform is as follows: https://tracking.bucksense.com/ts_p? transaction_id={param1}
The parameter {param1} should be replaced by any parameter you want to use.
Bucksense suggests to use HTTPS connections to track the conversions generated in your campaigns.
HTTP connections can be alternatively used: http://tracking.bucksense.com/ts_p? transaction_id={param1}

Example URL can be: https://www.example1.com/lp.php?param1={transaction_id}
In accordance with the tracking URL, the parameter ‘param1’ should be replaced by any value you want to use.
Your tracking system will then replace this macro with the value that was passed to the URL defined within the Bucksense offer.

Image Pixel

In case of Image Global Pixel, as well as for the Server to Server Post Back, your tracking system must have the ability to receive the Bucksense Transaction ID that can be passed to the URL defined in a Bucksense offer, in any parameter you require, with the macro {transaction_id}.
If you chose to implement the Image Global Pixel you must ensure that all of the URLs that you define within your offers in the Bucksense platform include this macro.

The code to insert in your tracking platform is as follows:
<img src=”https://tracking.bucksense.com/ts_p?transaction_id={param1}” width=”1″ height=”1″ />
Bucksense suggests to use HTTPS connections. HTTP connections can be alternatively used:
<img src=”http://tracking.bucksense.com/ts_p?transaction_id={param1}” width=”1″ height=”1″ />

Example URL can be: https://www.example1.com/lp.php?param1={transaction_id}.
As you can see from the above example, we’ve set the macro {param1} in transaction_id.
Your tracking system will then replace this macro with the value that was passed to the URL defined within the Bucksense offer.

A different Example URL is:
https://www.example1.com/lp.php?aff_sub={transaction_id}
and here is what the code to insert in your tracking platform would look like following this example:
<img src=”https://tracking.bucksense.com/ts_p?transaction_id={aff_sub}” width=”1″ height=”1″ />

iFrame Pixel

If you chose to implement the iFrame Pixel, in addition to the Bucksense Transaction ID, your tracking system must have the ability to receive the Bucksense Offer ID, which is an integer that can be passed to the URL defined in a Bucksense offer in any parameter you require.
We pass this value with the macro {offer_id}.
You must ensure that all of the URLs that you define within your offers in the Bucksense platform include these two macros.

The code to insert in your tracking platform is as follows:
<iframe src=”https://tracking.bucksense.com/ts_p?offer_id={param1}&transaction_id={param2}” scrolling=”no” frameborder=”0″ width=”1″ height=”1″></iframe>

As well as the Server to Server Post Back and the Image pixel, you can use HTTPS (suggested by Bucksense) or HTTP connections.

An Example URL is:
https://www.example1.com/lp.php?param1={offer_id}&param2={transaction_id}
where the macros {param1} and {param2} are set respectively in offer_id and transaction_id, and, our tracking system will then replace those macros with the values that were passed to the URL defined within the Bucksense offer.

Following the different example URL https://www.example1.com/lp.php?aff_sub={offer_id}&aff_sub2={transaction_id}, the code to insert in your tracking platform would look like:
<iframe src=”https://tracking.bucksense.com/ts_p?offer_id={aff_sub}&transaction_id={aff_sub2}” scrolling=”no” frameborder=”0″ width=”1″ height=”1″></iframe>

 

 

Offer Based Pixel with cookies and without cookies

We highly discourage you choose this option because it will mean that every time you set up a new Bucksense offer, you will need to setup the Bucksense Conversion Tracking Code in your tracking platform. The main difference between this option and the Global pixel option is that the Bucksense tracking pixel will always have the offer_id value populated.

However, if you must choose this option, you have two main options.

  • Tracking without cookies – using this method requires that your tracking system is able to receive the Bucksense Transaction ID.
  • Tracking with cookies – using this method doesn’t require your tracking system to receive the Bucksense Transaction ID.

Whichever your option is, once you’ve determined which one to go with,  you may retrieve the code to implement in your tracking system from the details of the offer page for which you are setting up this pixel for. To arrive there, please navigate as follows:

Click on Offers/Campaigns> Offer List in the Navigation Bar:

 

Then select the offer for which you will be setting up the Conversion Tracking. That will direct you to the Advanced Tracking page. There, scroll down to the bottom of the page and you will find the section that explains and provides the code:

Guideforconversiontracking2

Choose whether or not you’d like to use Cookieless Tracking or Tracking through Cookies.

Once you’ve selected the option, copy the code displayed on screen.

Use this code to either insert it into the 3rd Party tracking Platform you use or have someone within your development department help you add this code to the page you consider the “Success” page and therefore where the conversion will take place.

 

How to test your pixel

Especially for campaigns with the spend type Optimized (the option that lets Bucksense Smart Algorithm optimize your campaigns based on your conversion goal), we highly recommend that you test the pixel before activating your first campaign.

To make sure that Bucksense is receiving the pixel, you have to trigger a conversion using our test link.

  1. First, create your offer and enter your tracking link on Landing Page URL in Offer Details Section, write down the ID assigned to this offer and replace {yourOfferID} with the offer ID number in this link:
    http://click.bucksense.com/ts_c?ts7=1111&ts8=yourOfferID44
    In this example, your offer id is 16716 so your test link would be: http://click.bucksense.com/ts_c?ts7=1111&ts8=16716
  2. You then need to click the test link with a device, access the Landing Page URL and generate a conversion.
  3. Access the Offer Performance report below the Report Tab and click on Howtoaddanadvertiser9 Add filter button.
    Select Offer as filter, enter the Offer ID in the apposite field and click on Run report button555
  4. Check in the Report if the Conversion has been tracked
    vvvvvv

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *