Integrated partners can receive real-time postbacks about rejected installs due to fraud.
Rejected install postbacks due to fraud are sent to advertisers who are Protect 360 subscribers.
Integrated partners can receive postbacks about blocked installs due to fraud using one of the following methods:
- AppsFlyer can add additional parameters to the install postback. The additional parameters are Reject reason and Reject reason value (when available.) For example: rejected_reason=site_blacklist&rejected_reason_value="1123456"
- Create a new endpoint (a postback URL), dedicated to rejected installs, with a different structure. This includes the previously mentioned parameters and any other available parameters.
The following table lists the reject reason, reject reason value, and an explanation of the reject reason:
|Reject Reason||Reject Reason Value||Explanation|
|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 Partner Development Manager or email@example.com. Specify which of the two methods mentioned suits you.
If you want to add 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 Partner Development Manager or to firstname.lastname@example.org.