At a glance: Targeting validation and Protect360 custom fraud detection rules enable advertisers to reject install attribution of non-compliant installs. Integrated partners can view the rules and get reports of blocked installs.
By using validation rules, advertisers can reject the attribution of non-compliant installs. The rule types are as follows:
Targeting validation rules control campaign results. Installs that do not meet campaign targets are attributed as organic and are not attributed to the media source. Rules can be set using device type, OS, and geo.
Protect360 custom rules enhance Protect360's ability to detect fraudulent installs. Fraudulent installs are blocked and not attributed. Rules can be set using click time to install (CTIT), the presence of a customer user ID, and the app version.
- In the case of targeting rules where the install is invalid this means that it is not attributed to the media source and is shown as an organic install in AppsFlyer.
- In the case of Protect360, the install is blocked and has no attribution.
- In both cases, AppsFlyer can send the integrated partner real-time postbacks listing invalid and blocked installs.
Integrated partners can access the following enabling them to monitor the rules:
- View the validation rules that apply to campaigns running on their network
- Retrieve blocked/invalid install raw data reports
- Retrieve blocked/invalid install postbacks
To view the Validation Rules:
- In AppsFlyer, go to Configuration > Validation Rules.
The Validation Rules window opens and displays the list of rules that apply to the partner.
The following is displayed:
- Ruleset Owner: The name of the ruleset owner (usually the app owner). To display the ruleset, select App Owner. The ID is set by the app owner and displays in Validation Rules raw data reports/blocked install fraud reports, and the invalid install postbacks report.
- Ruleset Type: The ruleset type configured, either Targeting or Protect360.
- Media Source*: Shows the media source to which the ruleset is applied.
- Campaigns*: Shows the campaigns to which the ruleset is applied.
- Last Updated*: Shows the date on which the ruleset was last updated.
* Visible when the option is expanded by clicking the arrow.
- To view the validation rule, Select an App Owner.
The ruleset is displayed. For an explanation of how rulesets work see:
Targeting Validation Rules: export data
The following Raw Data reports can be downloaded from Reports > Export data:
- Invalid Installations means rejected installs
- Invalid Installations Postbacks means rejected installs
The Rejected Reason and Rejected Reason Value fields are populated in the Invalid Installations Report. The Rejected Reason Value includes the Ruleset ID that caused the rejection.
Protect360 Validation Rules: export data
Blocked installs as a result of the enforcement of Protect360 rules can be retrieved using the Blocked Fraud Reports, in Reports > Export data. The Blocked Reason and Blocked Reason Value fields are populated in the reports.
Validation Rules rejected installation postbacks
Integrated partners who integrate with AppsFlyer and receive blocked install postbacks in real-time each time an install is rejected due to enforcement of the rules.
Contact your Partner Development representative for further details.