Fraud Validation Rules - Airbridge Help Center

Fraud Validation Rules by Ad Fraud Types

Airbridge offers the following fraud validation rules to detect different types of ad fraud. Each rule operates independently.

Fraud Validation Rules	Description
Conversion Traffic	Detect suspicious events based on device information
Lag Time	Detect suspicious touchpoints based on the CTIT
Frequency Capping	Detect suspicious touchpoints based on the frequency of the touchpoint occurrence
IP Blocklisting	Detect suspicious touchpoints based on IP
SDK Signature	Detect suspicious events using SDK Signature credentials
Injection Prevention	Detect suspicious touchpoints that occur between app install and the first launch for Android apps

Prevention Levels

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.

Postbacks for suspicious events

When the Prevention Level is set to 2 or higher, suspected fraud events are excluded from postbacks. However, you can send them with limitations by completing the Postback settings below.

Data included in postbacks

Sends Target events only: Installs (App), Deeplink Opens (App), and Deeplink Pageviews (App).
Sends events as unattributed.
Sends the identified fraud type.

Eligible channels

Postbacks are sent to channels that would have received attribution if not suspected as fraud. These are channels that met all other Airbridge attribution model rules, including touchpoint priority and last-touch attribution (LTA).
Postbacks are sent only to channels with the Postback settings below configured.

Postback settings

In the postback delivery rule, set [Attribution] to All Events
Edit the postback URL as follows. If using the POST method, contact your CSM or reach out through the Airbridge Help Center.
- Add a postback parameter. Enter the parameter name specified by the channel and select {unattributedTouchpointFraudReason} as the parameter value.
- Some channels require {unattributedTouchpointClickID} as the Click ID parameter value. Confirm with the channel.

​Fraud Validation Rules by Ad Fraud Types

​Prevention Levels

Data included in postbacks

Eligible channels

Postback settings

Fraud Validation Rules by Ad Fraud Types

Prevention Levels