Suspicious events can be detected using the device information of the device to which the event is traced back.
The following device information can be used to detect suspicious events.
OS Version, App Version, Timezone, Country, Language, Locale, Network Carrier, IP Address
1. Navigate to [Settings]>[Fraud Validation Rules].
2. Select the [Conversion Traffic] tab and click Add a rule.
3. Configure [Property] and [Condition]. The following options are available.
3. Select the [Prevention Level] and click Save.
Attention
It is advised to start from "Prevention Level 1" and switch to higher levels after consulting with your media partner, as the prevention level setting may have a direct impact on the ad performance.
4. Click Add a rule to add more rules. When you have added multiple rules, any event that matches at least 1 of the configured rules will be treated as a suspicious event.
Suspicious events are processed according to the set prevention levels.
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.
Sends Target events only: Installs (App), Deeplink Opens (App), and Deeplink Pageviews (App).
Sends events as unattributed.
Sends the identified fraud type.
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.
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.
The suspicious events detected by the set rules can be viewed in your Airbridge reports and raw data export files.
In the Actuals Report, select "Conversion Fraud Tag" as a GroupBy to visualize the suspicious events tagged as fraud.
In the [App Raw Data Export], select "Conversion Fraud Tag" and "Fraud Tags" in the [Select Property] step to export suspicious events as a CSV file.
The following Conversion Fraud Tags are used to report suspicious events detected by the conversion traffic rules. The fraud tag names indicate the device information used for validation.
Fraud_Conversion_DeviceAOSVersion
Fraud_Conversion_DeviceiOSVersion
Fraud_Conversion_DeviceAppVersion
Fraud_Conversion_DeviceTimezone
Fraud_Conversion_DeviceCountry
Fraud_Conversion_DeviceLanguage
Fraud_Conversion_DeviceLocale
Fraud_Conversion_DeviceCarrier
Fraud_Conversion_DeviceIpAddress
Property |
Condition |
|---|---|
OS Version | Less than, Less than or equal to, Equal |
App Version, Timezone, Country, Language, Locale, Network Carrier, IP Address | In, Not In |
Prevention Level |
Description |
|---|---|
Level 1: Tag as fraud | - Suspicious events will be tagged as fraud in the Airbridge reports and raw data export files. |
Level 2: Don't send postbacks | - Suspicious events will be tagged as fraud in the Airbridge reports and raw data export files. - Suspicious conversions won't be sent as postbacks. |
Level 3: Don't attribute | - Suspicious events will be tagged as fraud in the Airbridge reports and raw data export files. - Suspicious events won't be sent as postbacks. - Suspicious events won't be attributed or aggregated. |
このページは役に立ちましたか？