Adgebra Help Center
About usFAQsAdvertisersPublishersLoginBlog
  • About Us
  • Getting Started
    • General
      • Why Advertise with Adgebra
      • Type of Accounts
      • Registration
      • Ad Formats
      • Adgebra Audience
      • Prepaid/Postpaid Accounts
      • Training & Support
    • Adgebra Wallet
      • Payment Methods
      • Payments T&C
    • Account
      • Details
    • Brand
      • Brand Specifications
      • Pixel Types
      • Postback Tracking
      • Adgebra Pixel using GTM
      • Blocking
    • Campaign
      • Information
      • Strategy
      • Scheduling & Targeting
      • Pricing & Budget
      • Blocking
      • Adding Creative
    • Troubleshooting
      • Campaign is not delivering
      • The campaign was running previously but has now stopped delivering.
      • The campaign is delivering, but not at its full potential.
      • Campaign Over-delivery
      • The campaign is not tracking conversions
      • Conversion Discrepancies
    • Creative
      • Creative Specifications
      • Impression Tracker
    • Reports
      • Placement Analysis
      • Detail Analysis
      • Trend Analysis
      • Conversion Analysis
      • Widget Analysis
      • Translation Summary
      • Partner API Report
      • Partner Widget API Report
    • Publisher
      • DIY Partner
      • Tag Placements
      • Partner Payment T&C
      • Partner API Integration
    • Site
      • Site Addition
      • Site Informartion
      • Ad Widgets
    • Traslator Guide
    • Adgebra oRTB
      • Overview
      • Terminology
      • RTB Ecosystem
      • RTB Basics
      • Win Notifications & User Syncing
      • Object Specification
    • Adgebra API Reports
      • Account Report API
      • Partner Report API
Powered by GitBook
On this page

Was this helpful?

  1. Getting Started
  2. Brand

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

  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 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}

https://testingpostback.com/click?sub1=${convId}

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}

https://testingpostback.com/click?p1=${convId}

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}

https://testingpostback.com/click?aff_click_id=${convId}

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}

https://testingpostback.com/click?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}

https://testingpostback.com/click?click_id=${convId}

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}

https://testingpostback.com/click?aff_click_id=${convId}

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}

https://testingpostback.com/click?subid=${convId}

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}

https://testingpostback.com/click?clickid=${convId}

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}

https://testingpostback.com/click?click_id=${convId}

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}

https://testingpostback.com/click?externalid=${convId}

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:

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

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

Steps :

- For AppsFlyer, handshake must be done with the client, you ask the client to share their af_part i.e, agency ID, and 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 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.

Postback Implementation with direct client thank you page

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/clicktracker/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

Postback Implementation with direct client thank you page

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.

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/clicktracker/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

Postback implementation with an intermediate platform: Hasoffers

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 the “trans” parameter. So, manually convert “convId=${convId}” to “trans=${convId}” in the landing page URL. In case of any confusion, talk to Hasoffers support team.

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

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

Example: https://hastracker.com/redirect?trans=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 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/clicktracker/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

Note:

  1. Conversion ID is in the form of a “string” (alphanumeric)

  2. The token ${convId} needs to be implemented for all language LPs of all creatives.

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

PreviousPixel TypesNextAdgebra Pixel using GTM

Last updated 18 days ago

Was this helpful?

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 above step to follow, please follow the detailed document for custom adjust integration: More detailed instructions can be found in the .

Example:

https://docs.google.com/document/d/10izxU6dc2Zvo5-9zAkZzo7VqmtM-mHCDd2l-Or7lDCU/edit?usp=sharing
Adjust Help Centre
https://caketracker.com/redirect?s2=100_67472_2_0_0_2405:205:8383:2aab:8f62:57a7:27ff:527f_3_1841