> ## Documentation Index
> Fetch the complete documentation index at: https://help.airbridge.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Fraud Validation Rules

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.

<Danger>
  **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.
</Danger>

## 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.

| <span style={{ display: 'inline-block', minWidth: '80px' }}>Fraud Validation Rules</span> | <span style={{ display: 'inline-block', minWidth: '200px' }}>Description</span>                    |
| ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Conversion Traffic](/en/guides/conversion-traffic)                                       | Detect suspicious events based on device information                                               |
| [Lag Time](/en/guides/lag-time)                                                           | Detect suspicious touchpoints based on the CTIT                                                    |
| [Frequency Capping](/en/guides/frequency-capping)                                         | Detect suspicious touchpoints based on the  frequency of the touchpoint occurrence                 |
| [IP Blocklisting](/en/guides/ip-blocklisting)                                             | Detect suspicious touchpoints based on IP                                                          |
| [SDK Signature](/en/guides/sdk-signature)                                                 | Detect suspicious events using SDK Signature credentials                                           |
| [Injection Prevention](/en/guides/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.

| <span style={{ display: 'inline-block', minWidth: '100px' }}>Prevention Level</span> | <span style={{ display: 'inline-block', minWidth: '200px' }}>Description</span>                                                                                                                                                                               |
| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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.<br />- 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.<br />- Suspicious events or touchpoints won't be sent as postbacks.<br />- Suspicious events or touchpoints won't be attributed or aggregated. |

<Accordion title="Postbacks for suspicious events">
  When the Prevention Level is set to 2 or higher, [suspected fraud events](/en/guides/fraud-validation-rules) are excluded from postbacks. However, you can send them with limitations by completing the [Postback settings](#postback-settings) below.

  ###### Data included in postbacks

  * Sends [Target events](/en/guides/airbridge-attribution-model#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](/en/guides/airbridge-attribution-model) rules, including touchpoint priority and last-touch attribution (LTA).
  * Postbacks are sent only to channels with the [Postback settings](#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](https://app.airbridge.io/supports).
    * 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.
</Accordion>

<link rel="alternate" hrefLang="en" href="https://help.airbridge.io/en/guides/fraud-validation-rules" />

<link rel="alternate" hrefLang="ko" href="https://help.airbridge.io/ko/guides/fraud-validation-rules" />