Event callbacks

Adjust sends an event callback every time a user completes an Adjust-reported in-app event. You need to set up event callbacks individually for each event token in your app.

Event names can always be modified in AppView, and so you should use the {event_name} placeholder as a human-readable label. Conversely, event tokens are permanent, and can always be referenced in your reporting as a constant identifier.

Recommended placeholder

{event}Event tokenbkrfgq
{event_name}Event name as set in AppViewpurchase_100_coins
If placeholder data is not available, it will be dropped from the callback.

Event callback example

Callback URL with placeholdersUnencoded (Do not use as is)
Callback URL populated with values

Other recommended placeholders

We also advise that you include the following placeholders in all callback URLs. These placeholders will ensure that you always receive basic information that you can use to identify the app, link, data point, and device to which the rest of your callback data belongs.

{gps_adid}Google Play Store advertising ID (Android only)38400000-8cf0-11bd-b23e-10b96e40000d
{idfa}ID for advertisers (iOS only)8C6CBCOD-5F43-4765-A6E6-84DFF3D24707
{idfv}ID for vendors (iOS only)CCB300A0-DE1B-4D48-BC7E-599E453B8DD4
{adid}Adjust device ID18546f6171f67e29d1cb983322ad1329
{tracker}Adjust link tokenabc123
{tracker_name}Current link name as defined in Campaign LabNetwork1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en
{app_name}Name of the appMyApp
{activity_kind}This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (cost_updated)rejected_reattribution
{created_at}The timestamp for when the data point occurred1404214665