Configuring Fraud Settings

Learn how to activate each of Singular's Fraud Protection Methods and configure their behavior.

See Singular Fraud Prevention for a description of each of the available methods.

To learn about user-defined rules and how to create them, see Configuring User-Defined Rules.


The core of the Singular Fraud Prevention Engine consists of two parts:

  1. Singular Protection Methods: These methods are built and refined by our fraud experts to protect against the most common types of fraud.
  2. User Defined Rules: Singular also supports the creation of custom rules to address each user's specific needs.

The Engine checks each end-user touchpoint (such as a click on an ad) against all of the Singular protection methods and any existing user-defined rules. If a touchpoint matches the definition included in a rule or method, the touchpoint is marked as whitelisted, rejected, or suspicious, according to the rule setting.

Whitelisted A touchpoint that is marked as whitelisted is considered valid and no other method or rule can marked it as rejected or suspicious.

If a touchpoint is rejected, Singular will not attribute an install to that touchpoint.

Suspicious Any touchpoint matching this rule/method is still considered valid for attribution but also marked as suspicious.

Note: The Engine marks a touchpoint based on the first rule that matches it, so the order of evaluation is important. Whitelisting rules are evaluated first to make sure any whitelisted touchpoint is not rejected. Then come rejection rules and finally suspicion rules.

Configuring Protection Methods

To manage the Protection Methods used in your account, go to Fraud Prevention > Settings.


The Fraud Settings page displays all the methods along with their associated actions. The actions dictate what happens when the protection method is triggered. Change the action and save the settings to change the behavior of the Fraud Engine immediately.

The possible actions are:

  • Do Nothing: If this action is chosen, the method is disabled and will not affect the attribution decision or reporting.
  • Mark as Suspicious: The method flags touchpoints as suspicious but doesn’t affect attribution decision.
  • Reject: The method rejects touchpoints and prevents CPI and CPA billing postbacks.
Was this article helpful?