How do I access information about the fraud cases found in my campaigns?
You can view your fraud data in several ways:
- For aggregated fraud data, Singular provides the following reporting pages:
- To view detailed data about every single fraud decision, you can download the raw logs of Singular's fraud prevention system. Go to Attribution > Export Logs and pick the Fraud log type. For more information, see the Export Logs and User-Level Data FAQ.
- To be notified in real time about fraud decisions, set up fraud postbacks to be sent to your internal BI dashboard. For more information, see the Fraud Postbacks FAQ.
What are the Rejected Report and the Suspicious Report?
The Rejected Report page (Fraud Prevention > Rejected Report) shows you how many installs were rejected, the estimated fraud CPI, and the estimated saved costs.
The report can be broken down by the rejection reason (the method or rule that caught the fraud attempt) as well as usual dimensions such as app, OS, campaign, and country.
The Suspicious Report page (Fraud Prevention > Suspicious Report) functions similarly to the Rejected Report, but shows installs that were marked as suspicious instead of being rejected.
Because the installs in this report were allowed to be attributed normally, you can also see cohort metrics about them, such as the revenue.
What is the Protected Report?
The Protected Report page (Fraud Prevention > Protected) gives you information about cases in which you were protected from a fraud attempt by Singular's fraud prevention system.
The installs in this report are legitimate installs. One or more of their associated touchpoints was rejected for fraud, but then Singular went on to find the legitimate touchpoint to which the install could be attributed.
Use this report to get additional information about where and how you are targeted by fraud. For example, you can see how many of your organic users are targeted, or whether a specific network or campaign have been targeted more than others.
What is the "Fraud Reason"?
The Reason dimension in fraud reports shows the name of the fraud method or custom rule that caused the install to be rejected or marked as suspicious.
Use this dimension to gauge the impact and usefulness of different rules.
What are "Estimated Fraud CPI" and "Estimated Saved Cost"?
These metrics are 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.
How is "Estimated Suspicious Cost" calculated (in the Suspicious Report)?
To estimate the suspicious cost (total cost for suspicious installs), we first find the CPI (cost per install) for the relevant app + OS + source (network) + date. This is the same CPI you can see in the Reports page, e.g.:
Then we multiply the CPI by the number of suspicious installs:
How do I get information about click IDs that have been marked as suspicious by Singular?
Singular customers and partner networks who want to investigate the click IDs found as suspicious can obtain a list through the Export Logs page.
- In the Singular web app or partner portal, go to Attribution > Export Logs.
- Select the log type Conversions and select the fields Partner, Click ID, Fraud Status, and Fraud Reason.
- Download the log and filter the table by Fraud Status = "Suspicious".