Fraud Prevention: Reporting

Rejected & Suspicious Reporting

These are two customized Singular Reporting views for Rejected or Suspicious Attributions. They include the same powerful flexible pivot functions and enable the analysis of Fraud that was prevented alongside the Rejection/Suspicious Reason and the Estimated Saved Cost which is available due to Singular’s unique cost data.

The Reason dimension which appears in both reports reflects the name of the Method/Custom Rule that has caused the rejection/suspicious flagging and can be used to gauge the effects and effectiveness of different rules.

The reports provide metrics for the amount and percentage of Rejected/Suspicious installs for the requested dimensions.

For example, a report generated for the App, Source and Rejection Reason dimensions with the Rejected Installs and Rejected Installs (%) metrics would show the following for each valid combination of app, source and reason:

  • The amount of Rejected Installs for the specific app, source, and reason.
  • The percentage of the rejected installs for the specific app, source and reason out of the total installs of the specific app and source.

Estimated Fraud CPI and Estimated Saved Cost are additional metrics that can be found only in the Rejected Report. They are defined as:

  • Estimated Saved Cost - an estimation of the cost of the fraudulent installs, based on the daily cost per source.
  • Estimated Fraud CPI - an estimation of the average CPI per fraudulent install, based on the estimated cost and number of rejected installs per source.

Protected Report

An attribution is considered protected if one or more of its associated touchpoints was rejected in the fraud prevention process. The protected report shows you these attributions and enables you to track who is targeted by fraud. For example, you can see how many of your Organic users are targeted or if a specific network or campaign are targeted more than others.

It’s important to remember that the “Sources” , “Campaigns” and “Publishers” shown in the protected report are of legitimate attributions that were protected by Singular Fraud Prevention.

Was this article helpful?
0 out of 0 found this helpful