The Postback Fallback conversion tracking method uses both the Postback URL and iFrame HTML pixel to provide you with the benefits of both Server-to-Server and browser based pixel tracking.
This Article Will Help You
- Know When to Use the Postback Fallback Method
- Understand the Conversion Pixel Logic
- Learn about Conversions From Whitelist Only
- Generate a Fallback Conversion Pixel
- Validate Postback Fallback Implementation
Section 1: When to use the Postback Fallback Method
This conversion tracking method should be used if you prefer to track conversions server-side for accuracy and other benefits, such as fraud prevention, but also need to support browser based pixels in order to piggy-back affiliate campaign pixels.
Since not all tracking platforms support Postback URL's, some networks and affiliates prefer to use HTML conversion pixels to allow for downstream piggy-backing capabilities. And because server tracking does not allow you to fire a browser-based HTML pixel, CAKE's Postback Fallback method is the best solution.
Section 2: Postback Fallback Pixel Logic
The Postback Fallback method works by firing both the Postback URL and the iFrame HTML pixel for the same user.
The Postback URL should be fired first so that CAKE will store the conversion from the server call.
CAKE should then receive the fallback iFrame pixel after the conversion has stored. This pixel call will come from the thank-you page where an affiliate's campaign HTML pixel will be piggy-backed.
Section 3: Conversions From Whitelist Only
For the best fraud prevention available within CAKE, be sure to use the Conversions From Whitelist Only setting alongside the Postback Fallback conversion tracking method.
With this Offer level setting enabled, CAKE will only store conversions from your server IP's which can be whitelisted in the CAKE Admin portal.
When used with the Postback Fallback method, if the iFrame fallback pixel is received before a conversion has been stored by the Postback URL from the whitelisted IP, the iFrame pixel will be ignored and have a disposition of "IP Not Whitelisted." In this scenario, the server call is the source of truth for storing conversions within CAKE.
To enable Conversions from Whitelist Only, follow these steps:
- Open the Offer card.
- Select the Redirect sub-tab.
- Check box for Conversions from Whitelist Only.
- Select Save at the bottom of the grid.
To whitelist server IP's, follow the steps below:
- Click on the Advertisers main tab
- Click on the Pixel Whitelist sub-tab.
- Click the Add button.
- Add the Advertiser entity.
- Add the Offer or select All Offers.
- Add the IP Start and IP End ranges.
- Check the Active box.
- Add a Note if necessary.
Section 4: Generate Postback Fallback Pixels
To generate the Postback URL, follow these steps from the Offer card:
- Click the Pixel button on the Home tab.
- Select Conversion/Install/Lead.
- Hit Next.
- Select and Copy the Postback URL.
To generate the Fallback iFrame pixel, follow these steps from the Offer card:
- Click the Pixel button on the Home tab.
- Select Conversion/Install/Lead.
- Hit Next.
- Choose Fallback from the Tracking Type* filter.
- Select and Copy the iFrame pixel.
Note: The Fallback pixel contains the fb=1 parameter which will force CAKE to recognize this pixel as a fallback instead of a duplicate pixel fire for the user.
Section 5: Validate in the Pixel Log
To verify the Postback Fallback conversion pixels are being recorded properly within CAKE, visit the Pixel Log.
The Pixel Log can be found by following the steps listed below:
- Click on the Advertisers main tab
- Click on the Pixel Log sub-tab
- Find the Offer you wish to validate
- Click on the Attempted number hyperlink
The Offer Pixel Log will appear which shows all pixel fires CAKE has received for that Offer. From here, you should be able to find the Postback URL pixel fire with a disposition of Conversion Stored. The line item above that should be the iFrame Fallback pixel that has a disposition of Pixels Fired On Postback Fallback.
Note: With the Conversions from Whitelist Only setting enabled, if the iFrame is received before the Conversion is stored from the Postback URL, the iFrame will be ignored and have a disposition of IP Not Whitelisted.