Integrated partners can receive postbacks containing data on installs that were rejected in real time due to fraud.
There are two ways integrated partners can receive the data.
- AppsFlyer can add two additional parameters to the install postback.
One informs you about the reject reason and the second informs you about the reject reason value when available. For example, rejected_reason=site_blacklist&rejected_reason_value="1123456"
- Alternatively, the integrated partner can choose to add a new endpoint (a postback URL) dedicated to rejected installs with a different structure that includes both of the above mentioned parameters as well as any other available parameter.
The below table specifies and explains the different Reject Reasons and Reject Reason Values:
|Reject Reason||Reject Reason Value||Description|
|devicerank||[Device ID]||DeviceRank identifies install fraud at the device-level. It blocks installs coming from Device IDs known to be perpetrating fraud.|
|ctit_anomalies||[The measured Click to Install Time in Seconds]||CTIT Anomalies are attributed clicks that have been blocked based on unreasonable CTIT (Click To Install Time).|
|Installs that failed validation from the App Store|
|site_blacklist||[Site ID]||Installs coming from Site IDs that AppsFlyer has blocked due to a high density of fraudulent activity, as determined by our internal algorithms|
|install_validation_rules||[Ruleset ID]||Installs which are defined as invalid by the advertiser using AppsFlyer's Validation Rules.
As an example the customer can define that he would like to promote his app only in the U.S. All installs coming from outside of the U.S. are considered as invalid and are rejected.
Blocked install attempt made by Bot
Installs coming from Site IDs that AppsFlyer has blocked due to a high amount of installs with high CTIT and low Conversion Rate.
Behavioral anomalies are install fraud installs, blocked due to inconsistent and abnormal post install behavior.
Install hijacking are attributed clicks that have been blocked based on unreasonable click and install time based on Google Play Server-Side API.
If you are integrated with AppsFlyer and want to start receiving postbacks on rejected installs, contact your dedicated Partner Development Manager or reach out to firstname.lastname@example.org. Specify which of the two methods mentioned above best suits your needs.
If you want to add two new parameters to your current postback, specify the parameter name as you would like to receive it such as, &rejected_reason and &rejected_reason_value.
If you want to add a completely new endpoint, send the new URL together with all relevant parameters to your dedicated Partner Development Manager or to email@example.com.