Overview

Singular’s Fraud Prevention Suite actively protects your marketing efforts using a mixture of out-of-the-box detection methods and custom user defined rules. Rejected installs won’t be attributed or reported to the partner preventing billing for CPI/CPA campaigns.

The fraud prevention process is comprised of 4 main steps:


At first all touchpoints relevant to the install are being collected. Touchpoints include every end-user event that might have led to the install, such as:

  • Clicks
  • Impressions (view-through)
  • Self Attribution Networks touchpoints from Facebook, AdWords, Twitter & Snapchat.
  • Google Play Install Referrer and additional special touchpoints

When the app is first opened an install event is triggered and sent to Singular’s servers, the install is logged and matching touchpoints are collected.

The Fraud Engine then receives the install event information alongside each of the touchpoints and based on the activated rules/methods and their respective actions, decides for each touchpoint if it is:

  • Valid - the touchpoint is valid and can be attributed to this install as usual.
  • Suspicious - the touchpoint is suspicious, which means it can still be used for attribution, but if used the attribution will be marked as suspicious and will appear in the suspicious report.
  • Reject - the touchpoint is rejected and it will not be used for attribution. Additionally, it will be reported in the rejected report.

Finally, based on the Fraud Engine’s decisions, a final attribution is made by choosing the highest priority touchpoints that is not rejected.

In the case that all touchpoints have been rejected the install would be attributed to Organic or Untrusted (read more in Untrusted Installs).

Every rejected touchpoint is counted and presented later on in the report, please pay attention that One Install can trigger multiple rejections.

Examples

Use Case #1

# Touchpoint

Type

Decision

Effect

1 - Highest Priority TP

Click

Rejected

Click #1 is being rejected and counted in the rejection reports.

2

Click

Valid

The Install is attributed to Click #2, postback will be sent to the relevant partner.

 

Use Case #2

# Touchpoint

Type

Decision

Effect

1 - Highest Priority TP

Click

Rejected

Click #1 is being rejected and counted in the rejection reports.

2

Click

Suspicious

The Install is attributed to Click #2 but marked as Suspicious, postback will be sent to the relevant partner.

 

Special Cases

One Install can trigger multiple rejections

Once the Fraud Engine finishes evaluating all the touch points - every touchpoint that has been considered rejected would be counted toward the rejections count.

This means that a single install might have multiple rejected touchpoints and would be counted more than once in the rejection reports.

#

Type

Decision

Effect

1 - Highest

Click

Rejected

Click #1 is being rejected and counted in the rejection reports.

2

Click

Rejected

Click #2 is being rejected and counted in the rejection reports.

3

Click

Valid

The Install is attributed to Click #3, postback will be sent to the relevant partner.

 

Untrusted Installs

In case the install itself is rejected (for example - comes from a blacklisted IP and the system is set to reject on blacklisted IPs) - the install will be attributed to Untrusted and marked as suspicious.

We exclude these installs from Organics because a rejected install is a characteristic of a bot and we want to enable their tracking without polluting the Organics report.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.