Rejected install or reattribution callbacks
The Fraud Prevention Suite detects and rejects fraudulent engagements before attribution. It includes Adjust's Anonymous IP Filter, Click Injection Filtering, and Distribution Modeling.
If you add
rejected_reattribution_callback to a link URL and the Fraud Prevention Suite detects fraud, you will see the rejection reason in the callback. See the following table for a list of the rejection reasons:
|Anonymous IP filtering|
|Click spamming - distribution modeling|
|Click spamming - hyper engagement|
|Click injection filtering|
Example: For an install matched to two clicks where one click is fraudulent and the second click is valid: The fraudulent click triggers a rejected install callback and the valid click triggers an install callback.
|Reason for a rejected install or reattribution|
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|