Postback Tracking
Postback Tracking
A "postback" in the context of digital marketing and web development refers to the process where a server sends data back to another server (or itself) to inform it about a specific event or action that has occurred. Here are the different contexts in which "postback" is used:.
How Postback Conversion Works
User Clicks an Ad: When a user clicks on an ad, a click ID (a unique identifier) is generated and associated with that click. This click ID is tracked by the advertiser's system.
User Completes a Conversion Event: After clicking the ad, if the user completes a desired action (like making a purchase or installing an app), this event is tracked by the advertiser's system.
Server-to-Server Communication: The advertiser's server sends a postback to the affiliate network's or partner's server. This postback contains the click ID and information about the conversion event.
Attribution: The affiliate network or partner uses the click ID to match the conversion event with the original click, thus attributing the conversion to the correct source.
Multiple clients use different third-party platforms and the configuration changes for each of these. The most important thing when working with a tracking platform is to map the click ID token with the Adgebra conversion ID.
Implementation Steps for various third-party platforms with Adgebra
Affise: In this case, the brands/advertisers need to map the click ID token i.e (sub1) in the Affise to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={sub1}
Landing Page URL: To ensure that the click ID (sub1) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Trackier: In this case, the brands/advertisers need to map the click ID token i.e (p1) in the Trackier platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={sub1}
Landing Page URL: To ensure that the click ID (p1) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Hasoffers: In this case, the brands/advertisers need to map the click ID token i.e. (aff_click_id) in the Hasoffer platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={aff_click_id}
Landing Page URL: To ensure that the click ID (aff_click_id) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Singular: In this case, the brands/advertisers need to map the click ID token i.e (convid) in the Singular platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={convid}
Landing Page URL: To ensure that the click ID (convid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Branch.IO this case, the brands/advertisers need to map the click ID token i.e (click_id) in the Branch.IO platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={click_id}
Landing Page URL: To ensure that the click ID (click_id) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Additional Placeholders: ~campaign_id=${campaignId} &~secondary_publisher=${siteId}
Offers18: In this case, the brands/advertisers need to map the click ID token i.e (aff_click_id) in the Offers18 platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={aff_click_id}
Landing Page URL: To ensure that the click ID (aff_click_id) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Additional Placeholders: &aff_sub1=${siteId} &aff_sub2=${campaignId}
Keitaro: In this case, the brands/advertisers need to map the click ID token i.e (subid) in the Keitaro platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={subid}
Landing Page URL: To ensure that the click ID (subid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Voluum: In this case, the brands/advertisers need to map the click ID token i.e (clickid) in the Voluum platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={clickid}
Landing Page URL: To ensure that the click ID (clickid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Trackier MMP: In this case, the brands/advertisers need to map the click ID token i.e (click_id) in the Trackier MMP platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={click_id}
Landing Page URL: To ensure that the click ID (click_id) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Offerborn: In this case, the brands/advertisers need to map the click ID token i.e (externalid) in the Offerborn platform to Adgebra’s conversion tracking ID (convId).
https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId={externalid}
Landing Page URL: To ensure that the click ID (clickid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (convId) as follows:
Appsflyer: If any client wants to integrate via Appsflyer just follow this step.
Steps :
- We are directly integrated with AppsFlyer so please search Partner: INUXUDMT
- Integrate with our partner id & generate a attribution link( LP).
- Get the attribution link (LP) from the client and you can add the same in the creative LP.
Note—If the client's platform is the existing one from the above, check if the value remains the same or needs to be changed and mapped accordingly.
Note:
Conversion ID is in the form of a “string” (alphanumeric)
The token ${convId} needs to be implemented for all language LPs of all creatives.
In case of multiple hops in the redirection of the trackers to landing page URLs, the settings need to be done in the intermediate tools/platforms in such a way that the conversion ID generated from Adgebra gets forwarded till the ultimate landing page URL. Likewise, the same conversion ID should be passed to Adgebra’s postback URL.
Feel free to reach out to your account manager for any clarifications or assistance.
Last updated
Was this helpful?