Before you begin
Set up pixel integration
In your offer, set up a Tracking URL on the Tracking tab. In pixel integration, this URL usually leads to an advertiser's product or service. You don't need to add any parameters and macros.
On the Postbacks tab, select the necessary pixel type. Update it with additional parameters, if necessary.
⚠️ Pixel tracking is based on a cookie file integrated into the Affise tracking domain. Make sure you use the same tracking domain in the Affise pixel and Affise tracking link. This ensures the correct work of a cookie file and the whole integration.
Example of using additional parameters for Image pixel:
<!--Offer Conversion: Offer -->
<img
src="https://rocketcompany.go2affise.com/success.jpg?offer_id=802&afid={afid}&afprice={afprice}&afgoal={goal}&afua={useragent}&afcomment={comment}&afstatus=1&afsecure=ff87d311f555f103683dc49b6ff393a2&custom_field1={extra_data}&custom_field2={extra_data}" height="1" width="1" alt=""/>
<!-- End Offer Conversion -->
Example of using additional parameters for JS pixel:
<!--Offer Conversion: Offer -->
<script language="JavaScript" type="text/javascript">var afoffer_id =802;
var afid={afid};
var afprice={afprice};
var afgoal={goal};
var afua={useragent};
var afcomment={comment};
var afstatus=1;
var afsecure=ff87d311f555f103683dc49b6ff393a2;
var custom_field1={extra_data};
var custom_field2={extra_data};
</script>
<script language="javaScript" type="text/javascript" src="https://rocketcompany.go2affise.com/track.js"></script>
<!-- End Offer Conversion -->
Example of using additional parameters for Iframe pixel:
<!--Offer Conversion: Offer -->
<iframe src="https://rocketcompany.go2affise.com/success..php?offer_id=131&afid={afid}&afprice={afprice}&afgoal={goal}&afua={useragent}&afcomment={comment}&afstatus=1&afsecure=ff87d311f555f103683dc49b6ff393a2&custom_field1={extra_data}&custom_field2={extra_data}" height="1" width="1" />
<!-- End Offer Conversion -->
Example of using additional parameters for Adwords pixel:
<!--Offer Conversion: offer_name -->
<script language="JavaScript" type="text/javascript">
var afid={afid};
var afprice={afprice};
var afgoal={goal};
var afua={useragent};
var afcomment={comment};
var afstatus=1;
var afsecure=ff87d311f555f103683dc49b6ff393a2;
var custom_field1={extra_data};
var custom_field2={extra_data};
</script>
<script language="JavaScript" type="text/javascript" src="https://rocketcompany.go2affise.com/gclid.js"></script>
<!-- End Offer Conversion -->
By default, the system fires an advertiser pixel in the pending (2) status. To receive conversions in a certain status, use the additional parameter afstatus=status and replace status with a certain conversion status value.
3. Send the pixel to your advertiser. They should implement it on the success page. If there is a JS pixel, it's implemented to the landing page and the success page.
🔎 Use a secure (HTTPS) tracking domain in any type of pixel. If you use the HTTP type of connection, clickid can be not recorded in cookies.
🔎 If you have more than one goal in the offer, and you want to track all goals, you should install the pixel separately for each goal.
Set up cookieless tracking
Some browsers like Safari and Firefox can consider Affise cookie a third-party one and don't support third-party cookie files at all. This makes the whole integration process impossible in some cases. Affise offers the solution: direct pixel tracking using the cookie file integrated into the offer domain.
There are two options for your workflow. Do either Option 1 or Option 2.
Option 1
Add the clickid parameter and the {clickid} macro to an advertiser tracking link. In pixel integration, it is just a link to the offer landing page. You don't need to get the parameter for the click ID value from your advertiser.
Take and update the JavaScript pixel in Offers > a certain offer > Postbacks > JavaScript, and share it with your advertiser.
An advertiser should set the first part of a JS code to the offer (landing) page after the opening
<body>tag.An advertiser set the second part of a JS code to the offer success (thank you) page.
The code on the landing page extracts click ID and stores it in the cookie file saved in the local storage, instead of the Affise tracking domain. The system saves the cookie file not when redirecting to the Affise tracking link, but when reaching the landing page. The third part doesn't participate here.
Option 2
Take and update the JavaScript (Direct) pixel in Offers > a certain offer > Postbacks > JavaScript, and share it with your advertiser.
An advertiser should set the first part of a JS code to the offer (landing) page after the opening
<body>tag.An advertiser should add the &pid={pid} parameter to the URL of the landing page pixel (to define an affiliate). As you don't use an Affise tracking link, determination of the affiliate is required at this stage.
An advertiser should set the second part of a JS code to the offer success (thank you) page.
Since you don't use an Affise tracking link, the system initiates the click by making a request right to the landing page. This request returns the click ID saved in the local storage. This is why the JS code on the landing page is obligatory.
⚠️ Make sure you use the same domain in the code for the landing and the success pages.
What to do next
📃 Related topics
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].