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

1. 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.

2. 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.

3. 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.

4. 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 to work 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

In this case, the brands/advertisers needs to map the click ID in 3rd party platform to Adgebra’s conversion tracking ID (convId).

1. 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).

Here’s how the postback URL is set up :

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:

Landing Page: https://testingpostback.com/click?sub1=${ConvId} 

2. Trackier : 

In this case, the brands/advertisers needs to map the click ID token i.e (click_id) in the Trackier platform to Adgebra’s conversion tracking ID (ConvId).

Here’s how the postback URL is set up :

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 (p1) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (ConvId) as follows:

Landing page - https://testingpostback.com/click?click_id=${ConvId} 

Additional Placeholder that can be used are also : P2=${siteId}

3. 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).

Here’s how the postback URL is set up :

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:

Landing page - https://testingpostback.com/click?aff_click_id=${ConvId} 

4. 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).

Here’s how the postback URL is set up :

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:

Landing Page - https://testingpostback.com/click?convId=${ConvId} 

5. Branch.IO:

In 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).

Here’s how the postback URL is set up:

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:

Landing page - https://testingpostback.com/click?click_id=${ConvId} 

Additional Placeholders: ~campaign_id=${campaignId}  &~secondary_publisher=${siteId} 

6.  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).

Here’s how the postback URL is set up :

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:

Landing page - https://testingpostback.com/click?aff_click_id=${ConvId} 

Additional Placeholders: &aff_sub1=${siteId}  &aff_sub2=${campaignId}

7. 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).

Here’s how the postback URL is set up :

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:

Landing Page : https://testingpostback.com/click?subid=${ConvId} 

8. 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).

Here’s how the postback URL is set up :

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:

Landing Page : https://testingpostback.com/click?clickid=${ConvId} 

9. 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).

Here’s how the postback URL is set up :

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:

Landing Page : https://testingpostback.com/click?click_id=${ConvId} 

10. 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).

Here’s how the postback URL is set up :

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:

Landing Page : https://testingpostback.com/click?externalid=${ConvId} 

11. Icubeswire: 

In this case, the brands/advertisers need to map the click ID token, i.e, (aff_click_id) in their platform to Adgebra’s conversion tracking ID (ConvId).

Here’s how the postback URL is set up :

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 (clickid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (ConvId) as follows:

Landing Page : https://tracking.icubeswire.co/aff_c?aff_click_id=${ConvId} 

12. Indixital: In this case, the brands/advertisers need to map the click ID token, i.e, (p4), in their platform to Adgebra’s conversion tracking ID (ConvId).

Here’s how the postback URL is set up :

https://adgebra.co.in/clicktracker/conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&ConvId={p4}

Landing Page URL: To ensure that the click ID (p4) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (ConvId) as follows:

Landing Page : https://t.indixital.com/r?c=1610&p=121&p1=AZ1&p3=AZ1&p4=${ConvId} 

13. Adjust:  All partners integrated with Adjust can be found under Campaign Lab > Partners. From there, clients should:

1. Select + New partner

2. Search for Adgebra in the search bar

3. Select the Adgebra tile

4. Click Next

5. Follow the wizard to enable the integration and generate an Adjust link for Adgebra

6. Get the adjust link from the client and use as LP in the creative ad copy. Here before you use the link you need to pass the token as mentioned below

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:  Please note here you need to pass the token before the install_callback 

Landing Page Sample - https://app.adjust.com/1mbeh5l7?campaign=vb-acquisition_cpr-programmaticmobupps-TabunganU&adgroup=7796_218&creative=Mobupps_CO&idfa={ios_ifa}&gps_adid={google_aid}&language={aff_sub4}&android_id={android_id}&ip_address={ip}&user_agent={user_agent}&click_id=${ConvId}&install_callback=https%3A%2F%2Fadgebra.co.in%2Fclicktracker%2Fconversion%3Fp2%3Dorder_Id%26p3%3Dproduct_Id%26p4%3Dcartvalue%26p5%3Dflag_custom_values%26convId%3D{click_id}

If any client wants custom integration and doesn't want the above step to follow, please follow the detailed document for custom adjust integration: https://docs.google.com/document/d/10izxU6dc2Zvo5-9zAkZzo7VqmtM-mHCDd2l-Or7lDCU/edit?usp=sharing

More detailed instructions can be found in the Adjust Help Centre.

14. Appsflyer:  If any client wants to integrate via Appsflyer, just follow this step.

Steps : 

- For AppsFlyer, a handshake must be done with the client, you ask the client to share their af_part i.e, agency ID,  inform the product team to whitelist the agency id. Then, only the agency would be able to integrate with us. 

- Next is 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.

-Get the attribution link from the client and use it as LP in the creative ad copy. Here before you use the link you need to pass the token as mentioned below

-Landing Page URL: To ensure that the click ID token  (clickid) gets mapped correctly upon the user’s click, the landing page URL should pass the conversion ID (ConvId) as follows:

Landing Page Sample : https://navi.onelink.me/Nerp?pid=inuxudmt_int&c=PL_edge_Adgebra&af_siteid=${siteId}&af_cost_model=cpc&af_cost_value=5&af_cost_currency=INR&af_ad_type=native&af_c_id=${campaignId}&url=HOME-DASHBOARD-Loans&af_click_lookback=7d&deep_link_value=HOME-DASHBOARD-Loans&clickid=${ConvId}

Note -  If the platform used by the client is the existing one from the above, check if the value remains the same or needs to be changed and mapped accordingly. 

Step 1: Generate conversion post-back URL from UI (same screen where conversion pixel can be generated)

Step 2: In Creative LP, add a token ${convId}  

Step 3: On click of the ad, the token will get replaced with the actual conversion Id.

Example: https://landingpage.com/checkout?convId=1100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_184 

Step 4: On conversion, the client needs to call the post-back URL generated in step 3 with the actual conversion ID against the convId parameter sent on the landing page by Adgebra

Example: http://adgebra.co.in/Tracker/Conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841 

Step 1: Generate conversion post-back URL from UI (same screen where conversion pixel can be generated)

Step 2: In Creative LP, add a token ${convId} but it should be placed against s2 parameter. So, manually convert “convId=${convId}” to “s2=${convId}” in the landing page URL. In case of any confusion, talk to Cake support team.

Example : https://caketracker..com/redirect?s2=${convId} 

Step 3: On click of ad, the token will get replaced with actual conversion ID in the cake tracker.

Example:https://caketracker.com/redirect?s2=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841

Step 4: On conversion, client needs to call the post-back URL of Cake and Cake should further give a call to adgebra’s postback URL with actual conversion ID generated in step 3.

Example:http://adgebra.co.in/Tracker/Conversion?&p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841

Step 1: Generate conversion post-back URL from UI (same screen where conversion pixel can be generated)

Step 2: Add a token ${convId} in Creative LP, but it should be placed against the “aff_click_id” parameter. So, manually convert “convId=${convId}” to “trans=${convId}” in the landing page URL. In case of any confusion, talk to the Hasoffers support team.

Example: https://hastracker..com/redirect?trans=${convId} 

Step 3: On click of the ad, the token will get replaced with the actual conversion ID in the Hasoffers tracker.

Example:https://hastracker.com/redirect?aff_click_id=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841

Step 4: On conversion, the client needs to call the post-back URL of Hasoffers, and Hasoffers should further give a call to Adgebra’s postback URL with actual conversion ID generated in step 3.

Example:http://adgebra.co.in/Tracker/Conversion?p2=order_Id&p3=product_Id&p4=cartvalue&p5=flag~custom_values&convId=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841