At a glance: Targeting validation and Protect360 custom fraud detection rules enable advertisers to block 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 campaign name, device type, OS, and geo.
- Targeting validation rules: If the install is invalid it means that it is not attributed to the media source and is shown as organic in the platform.
- The platform sends real-time postbacks listing invalid installs
Protect360 custom rules enhance Protect360's ability to detect fraudulent installs.
- Fraudulent installs are blocked and not attributed. In the case of hijacked installs, the attribution media source is corrected and the install is not blocked. Rules can be set using click time to install (CTIT), the presence of a customer user ID, and the app version.
- Fraudulent installs are blocked, meaning they are not attributed to the media source. This does not impact the installation or use of the app by the user.
- Hijacked installs are not blocked and their attribution is corrected.
- The platform can send real-time postbacks listing blocked installs
Integrated partners can access the following enabling them to monitor the rules:
- View the validation targeting rules and Protect360 CTIT rules that apply to campaigns running on their network. Note: Partners can't view user ID and app version rules.
- 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.