Updated attribution callbacks
Updated attribution callbacks are fired whenever a user’s attribution changes after the initial install attribution or reattribution. This usually occurs when a self-attributing partner, such as Google or Facebook, claims an install after we have already attributed it to another source. We also send updated attribution information after an iOS 14.5+ device's ATT status changes to Authorized.
Add the following placeholders to your callback URL to receive updated attribution information in your raw data.
|Adjust link token for the original source of attribution.||abc123|
|Link name of the user’s initial attribution.||example-link|
|Updated attribution timestamp||1403566587|
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.
|Google Play Store advertising ID (Android only)||38400000-8cf0-11bd-b23e-10b96e40000d|
|ID for advertisers (iOS only)||8C6CBCOD-5F43-4765-A6E6-84DFF3D24707|
|ID for vendors (iOS only)||CCB300A0-DE1B-4D48-BC7E-599E453B8DD4|
|Adjust device ID||18546f6171f67e29d1cb983322ad1329|
|Adjust link token||abc123|
|Current link name as defined in Campaign Lab||Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en|
|Name of the app||MyApp|
|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 (||rejected_reattribution|
|The timestamp for when the data point occurred||1404214665|