Callback structure

Learn about the different parts that make up a callback URL and understand how they all work together. Understanding the structure of a callback will help you better set them up.

Parts of a callback URL

To set up a callback, you need to specify:

• The server endpoint URL where you want to receive data. This should be tied to your own business intelligence solution or data warehouse to process callbacks.
  • Some partners only share campaign information over HTTPS. We recommend using https:// for all callback URLs. Example: https://serverendpoint.com/mobile_attribution
• Device identifiers - idfa, gps_adid, adid
• Callback parameters for the data points that you want to measure - tracker_token, tracker_name, app_name, activity_kind
• Adjust placeholders for the data points that you want to measure - {tracker}, {tracker_name}, {app_name}, {activity_kind}

You can add as many parameters and placeholders to your callback string as you like — just separate each key-value pairing with an ampersand (&). When you set up your callbacks, keep our recommended placeholders in mind. These will help you measure the data points that are most relevant to your needs.

https://serverendpoint.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&idfv={idfv}&adid={adid}&tracker_token={tracker_token}&tracker_name={tracker_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&event_token={event}&event_name={event_name} 

String placeholders

It is also possible to string placeholders together to receive grouped values. You can do this by using a hyphen (-) between placeholders. This is useful for contextually related information, such as language and region.

https://serverendpoint.com/mobile_attribution?language_region={language}-{region}