Self-attributing network callbacks

Self-attributing network click and impression callbacks are fired on every multi-touch click / impression reported by a self-attributing network.

Recommended placeholders

Any relevant advertising IDs and/or device IDs (e.g., {idfa}, {gps_adid}, {idfv}, {adid})*Advertising IDs and/or device IDs (used to map multi-touch clicks and impressions with resulting installs, sessions, and events)8C6CBCOD-5F43-4765-A6E6-84DFF3D24707, 38400000-8cf0-11bd-b23e-10b96e40000d, CCB300A0-DE1B-4D48-BC7E-599E453B8DD4, 18546f6171f67e29d1cb983322ad1329
Any relevant Google, Facebook, and/or Twitter specific placeholders (see Adjust’s placeholder list)Specific placeholders for each self-attributing network where you are running campaignsvaries
If placeholder data is not available, it will be dropped from the callback.

Callback example

Callback URL with placeholdersUnencoded (Do not use as is)
Callback URL populated with values{gps_adid}&idfa={idfa}&idfv={idfv}&adid={adid}&tracker_token={link_token}&tracker_name={link_name}&app_name={app_name}&created_at={created_at}&facebook_campaign={fb_campaign_group_name}&facebook_campaign_id={fb_campaign_group_id}&google_campaign={google_ads}&google_campaign_id={google_ads_campaign_id}

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