Detect and fight ad fraud by configuring fraud validation rules. You can set the prevention level for each rule and decide how to process the fraudulent conversions and touchpoints.
Caution
The fraud validation rules may affect ad cost calculations for paid ads. Consult with your ad channels, agencies, and any other stakeholders before configuring the fraud validation rules.
Airbridge offers the following fraud validation rules to detect different types of ad fraud. Each rule operates independently.
Fraud Validation Rules |
Description |
|---|---|
Detect suspicious events based on device information | |
Detect suspicious touchpoints based on the CTIT | |
Detect suspicious touchpoints based on the frequency of the touchpoint occurrence | |
Detect suspicious touchpoints based on IP | |
Detect suspicious events using SDK Signature credentials | |
Detect suspicious touchpoints that occur between app install and the first launch for Android apps |
Suspicious events and touchpoints detected by the fraud validation rules will be processed according to the set prevention levels.
Prevention Level |
Description |
|---|---|
Level 1: Mark as fraud | - Suspicious events or touchpoints will be tagged as fraud in the Airbridge reports and raw data export files. |
Level 2: Don't send postbacks | - Suspicious events or touchpoints will be tagged as fraud in the Airbridge reports and raw data export files. - Suspicious conversions or touchpoints won't be sent as postbacks. |
Level 3: Don't attribute | - Suspicious events or touchpoints will be tagged as fraud in the Airbridge reports and raw data export files. - Suspicious events or touchpoints won't be sent as postbacks. - Suspicious events or touchpoints won't be attributed or aggregated. |
Was this page helpful?