In order to ensure you track successfully with Offermetrix, 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.
Conversion events vary by business, but usually are one of the following:
- Lead
- Sale
- Subscription
- Email opt-in
- Installation
- In-app purchase
How to implement the Conversion Pixel
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 OfferMetrix tracking system only once.
That way, any offer that you would like to have promoted within OfferMetrix 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 OfferMetrix 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 platform include this macro.
The URL to insert in your tracking platform is as follows: https://tracking.offermetrix.com/ts_p?transaction_id={param1}
The parameter {param1} should be replaced by any parameter you want to use.
OfferMetrix suggests to use HTTPS connections to track the conversions generated in your campaigns.
HTTP connections can be alternatively used: http://tracking.offermetrix.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 OfferMetrix 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 Transaction ID that can be passed to the URL defined in a OfferMetrix 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 platform include this macro.
The code to insert in your tracking platform is as follows:
<img src=”https://tracking.offermetrix.com/ts_p?transaction_id={param1}” width=”1″ height=”1″ />
OfferMetrix suggests to use HTTPS connections. HTTP connections can be alternatively used:
<img src=”http://tracking.offermetrix.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 OfferMetrix 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.offermetrix.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 OfferMetrix Transaction ID, your tracking system must have the ability to receive the Offermetrix Offer ID, which is an integer that can be passed to the URL defined in a 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 OfferMetrix platform include these two macros.
The code to insert in your tracking platform is as follows:
<iframe src=”https://tracking.offermetrix.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 OfferMetrix) or HTTP connections.
An Example URL is:
https://www.example1.com/lp.php?param1={offer_id}¶m2={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 OfferMetrix 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.offermetrix.com/ts_p?offer_id={aff_sub}&transaction_id={aff_sub2}” scrolling=”no” frameborder=”0″ width=”1″ height=”1″></iframe>