Singular's Fraud Prevention Engine identifies various types of ad fraud - from click injection and fake installs to custom, user-defined fraud symptoms - to ensure that Singular attribution decisions are not influenced by fraud attempts.
The Fraud Prevention Engine ensures that your data reflects your real marketing performance and that you are not billed excessively for CPI/CPA campaigns.
Management, UA teams
|Prerequisites||Singular attribution is set up for your account|
Step by Step
Understand the Different Protection Methods
Singular offers a rich menu of pre-existing fraud protection methods that detect different types of fraud. For example, the "Blacklisted IPs" method detects clicks and installs coming from IPs that are associated with fraud (such as VPNs).
If you enable a fraud method, it will be used to evaluate all the clicks and impressions that are candidates for attribution before a final attribution decision is made. However, not all methods are useful for all verticals, geographic locations, etc. This is why we give you the freedom to enable or disable each method separately.
To learn more about each method, see List of Fraud Protection Methods.
Note: Singular also protects you against click-flooding attacks. Click flooding protection is enabled automatically and you don't need to set it up.
Learn more in the Click Flooding Protection FAQ.
Set Up Your Protection Methods
To manage the methods used in your account, go to Fraud Prevention > Settings, go over the methods, and for each one choose the relevant action:
Best Practices: Use “Mark as Suspicious” Before Enabling “Reject”
Singular's fraud prevention tools - including both the default method and any custom rules - may run into edge cases and produce unwanted behavior in the form of false positives or false negatives. When you activate new methods or rules without testing them, they may affect your ongoing marketing campaigns or impact your volume unexpectedly.
This is why we recommend testing new methods and rules by setting them to "Mark as Suspicious" rather than "Reject". Monitor the performance of the methods/rules for a while, using the suspicious report, and make sure they work as expected.
Once you're satisfied with the methods/rules, promote them to "Reject" so that they prevent Singular from sending billing postbacks and help keep down your CPI/CPA charges.
Set Up Custom Rules (Optional)
In addition to the fraud protection methods developed by Singular, you can also create your own custom rules to prevent types of fraud that are specific to your apps.
For example, you may want to whitelist partners that are guaranteed to not fraud you, e.g., internal cross-promo. Or you may reject installs that don’t match your campaign’s targeting options.
To create a user-defined rule:
Ensure You are Using In-App Purchase Validation
In-App Purchase (IAP) validation is a process in which Singular evaluates revenue events in your apps (both Android and iOS) and detects invalid/fraudulent user purchases so that they do not skew your revenue metrics.
Learn more in the In-App Purchase Validation FAQ.
Set Up Fraud Postbacks (Optional)
Singular can send automated postbacks about fraud decisions to the relevant ad network and/or to the customer's internal BI platform.
There are two types of fraud postbacks:
See the Fraud Postbacks FAQ for more information and troubleshooting tips.
Leverage Singular Alerts (Recommended)
Singular lets you set up custom alerts on different KPIs so you can be automatically notified about sudden and/or significant changes in your data.
You can leverage alerts to track fraud in two ways:
Learn more in the Alerts FAQ.
Use Fraud Reports to Track Fraud Attempts
Singular’s fraud reports let you:
Learn more in the Fraud Reports and Fraud Logs FAQ.