In Everflow, there are three Conversion Methods to choose from. Each Offer must be configured with one of them. Essentially, the Conversion Method is the way in which conversions are tracked from the website or app to Everflow.
The available Conversion Methods are:
HTML Pixel / Cookie-Based (not recommended - unreliable and unsupported by many browsers)
For a quick guide to choosing between Direct Linking and Traditional Redirects - [Click Here]
The Server Postback method utilizes Postback URLs, which create a server-to-server connection for recording Conversions and Events in Everflow.
How Server Postback Works:
User clicks on Ad. Using the Everflow Tracking Link, that user data is fired to Everflow.
Everflow's Server generates a Transaction ID to identify the user's Click and passes it to the Advertiser/Brand.
**Please note that this requires the Advertiser/Brand to store the Transaction ID on their side.
Using a HTTPS GET request, the Advertiser/Brand must fire that Transaction ID to Everflow (via Postback URL) when the user completes a Conversion (i.e. downloads an app / makes a purchase / etc. ).
Server Postback Tracking Advantages:
Highly accurate, as it does not rely on browser-based tracking (i.e. third-party cookies).
Very secure, as Conversions are fired from the Advertiser/Brand's database, not the user's browser.
For more information on setting up a Postback URL with the Advertiser/Brand - [Click Here]
**Recommended for direct Offers, as you must be able to place JS scripts directly on the landing page and conversion page.
User clicks on Ad and is sent to landing page.
The EF.click script (i.e. a piece of code placed on the landing page) fires the Click to Everflow.
The EF.conversion script (i.e. a piece of code placed on the conversion/thank you page) fires the Conversion to Everflow when the user completes a Conversion (i.e downloads something, makes a purchase, etc.).
Easy implementation, simply copy and paste the scripts onto the landing and conversion pages.
Highly accurate, as it relies on first-party cookies via our SDK.
Allows Partners to promote through channels that prohibit third-party links, like Facebook and Google
Easily configurable for use with Google Tag Manager.
Compatible with built-in shopping cart integrations such as Shopify, WooCommerce, BigCommerce, etc.
For more information on setting up Direct Linking - [Click Here]
HTML Pixel / Third Party Cookie-Based
**We don't recommend this tracking method due to browser restrictions making it increasingly obsolete.
The HTML Pixel or Cookie-Based method is outdated and should not be used to track data back to Everflow in the majority of cases as it uses third party cookies, which are now blocked by most major browsers.
**For the most accurate results with cookie-based tracking, make sure that the tracking domain and conversion domain are the same.
How HTML Pixel Works:
Advertiser embeds an image pixel on the confirmation page of an offer (the page displayed after the tracked action has occurred).
User clicks on Partner Tracking Link to be redirected to the Offer.
A cookie is dropped on the Advertiser/Brand's site to identify that user's Click.
Pixel fires when confirmation page renders, pinging Everflow with the user's stored data from the cookie to match it with the click.
To increase reliability, add
&transaction_id= to the pixel.
How Third Party Cookie-Based Works:
User clicks on Ad. Using the EF.click script (i.e. a piece of code placed on the landing page) the Click is fired to and tracked in Everflow.
Everflow drops a cookie on the Advertiser/Brand's site to identify that user's Click, which is not stored in the user's browser. It is only stored in the third party cookie.
The EF.conversion script loads on the page when the user completes a Conversion (i.e downloads something, makes a purchase, etc.)
Conversion Postback Compatibility
Regardless of the conversion method selected in the offer, other advertiser postbacks will work as well:
Conversion Method in Everflow:
JS SDK or HTML Cookie
Server Postback, iframe, image source, JS SDK