We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Rejected install or reattribution callbacks

Growth solution:

The Fraud Prevention Suite is available as an Adjust Growth Solution. To get Fraud Prevention on your account, contact a sales@adjust.com.

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_install_callback or 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:

Rejection reason	Description
`anonymous_traffic`	Anonymous IP filtering
`distribution_outlier`	Click spamming - distribution modeling
`too_many_engagements`	Click spamming - hyper engagement
`engagement_injection`	Click injection filtering
`incorrect_signature`	Invalid Signature

Note:

It is possible for one attribution to trigger an install callback and a rejected install callback.
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.

Recommended placeholder

Placeholder	Description	Example
`{rejection_reason}`	Reason for a rejected install or reattribution	`anonymous_traffic`

Note:

If placeholder data is not available, it will be dropped from the callback.

Rejected install or reattribution callback example

Callback URL with placeholdersUnencoded (Do not use as is)

Callback URL populated with values

https://mynetworkserver.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&idfv={idfv}&adid={adid}&tracker_name={link_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&rejection_reason={rejection_reason}

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.

Placeholder	Description	Example
`{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 ID	18546f6171f67e29d1cb983322ad1329
`{tracker}`	Adjust link token	abc123
`{tracker_name}`	Current link name as defined in Campaign Lab	Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en
`{app_name}`	Name of the app	MyApp
`{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 occurred	1404214665