Validation Rules

You can set fraud validation rules and prevention levels for Touchpoint and Conversion from [ Management > Rule Configuration > Fraud Validation Rules ]. You can determine how to mark suspicious events by 3 levels: 'Mark as a Fraud', 'Disabled Postback' or Disabled Attribution'

Please be noted Fraud Validation Rules may affect the calculation of paid advertisements, thus the rules MUST be discussed and consulted with agencies and channels in advance.

 

Configurable Rule Types

Conversion Traffic

Detect fraudulent events based on the APP information in which conversion has occurred.

mceclip0.png

 

1. Rules are generated based on device information in which conversion has occurred.

  • OS Version: Android / iOS (e.g. : Android 5.0.2)

  • App Version : App version the user installed (e.g. : 1.2.3)

  • Timezone : Timezone of device (e.g. : Asia/Seoul)

  • Country : Country code of device (e.g. : KR(Korea, Republic of))

  • Language : Language code of device (e.g. : ko(Korean))

  • Locale : Locale information of device, Language/Country (e.g. : ko-KR)

  • Network Carrier : Network Carrier of device (e.g. : SKTelecom)

  • IP Address : IP address of device (e.g. : 61.33.15.194)

 

2. The following conditions are available for the selected properties.  

  • OS Version : Less than, Less than or equal to, Equal

  • App Version / Timezone / Country / Language / Locale / Network Carrier / IP Address : In, Not In

 

3. Choose the prevention level when the events are affected by the rules. You may refer to the following guide.

 

4. You can create multiple validation rules. All rules are reflected as 'OR' condition. 

 

Lag Time

Using the lag time between Touchpoint (Click, Impression) and App Installation, you can mark specific Touchpoints with abnormal lag time as fraudulent. You can create Lag Time rules per each Touchpoint type individually.

mceclip0.png

1. Select the type of Touchpoint (Click, Impression)

 

2. The following conditions are available for the selected property. 

  • 'Less than', 'Greater than'

 

3. Select unit of time as follows. 

  • 'Second(s)', 'Minute(s)', 'Hour(s)', 'Day(s)'

 

4. Choose the prevention level when the events are affected by the rules. You may refer to the following guide.

 

5. You can create multiple validation rules. All rules are reflected as 'OR' condition.

 

 

Frequency Capping

If touchpoints occur more often than the threshold value during the configured time, you can mark the touchpoints above the threshold as fraudulent touchpoints. You can apply specific IP, device, and sub-publisher on each touchpoint type. Follow the below guide to create your own Frequency Capping rules.

mceclip1.png

1. Select the type of Touchpoint (Click, Impression)

2. Select Property. (IP, Device, Sub-Publisher)

3. Type Capping value. (thresholds) 

4. Select time range. Time range is broken down into 1 minute unit up to 10 minutes, 5 minutes unit from 10 minutes to 55 minutes, and 1 hour unit from 1 hour to 24 hours.

5. Choose the prevention level when the events are affected by the rules. You may refer to the following guide.

6. You can create multiple validation rules. All rules are reflected as 'OR' condition.

 

Blacklisting IP

You can classify fraudulent events based on the IP where the touchpoint occurred. For example, you can exclude touchpoints that occurred from non-target countries or touchpoints occurred from AWS Server IPs that can be suspected as a bot traffic.

mceclip2.png

1. Select type of IP property. (Server IP, Country IP)

  • Server IP: These IPs registered in Airbridge DB are IP bands provided by cloud services such as AWS and GCP. Thus a normal user's device cannot generate such IP addresses. Should an event occurs in these IP bands, you could suspect it as a fraud. 
  • Country IP: You can select specific country's IP to include or exclude. 

2. Select Condition over the selected property. 

3. Select Country from the drop-down menu.

4. Choose the prevention level when the events are affected by the rules. You may refer to the following guide.

5. You can create multiple validation rules. All rules are reflected as 'OR' condition.

 

Setting Prevention Levels for Fraudulent Events

blobid0.png

Mark as a Fraud

When fraudulent events are detected by the configured rules, the touchpoints or conversions are marked as fraudulent. For this prevention level, attribution is acknowledged and postback is also sent to channels accordingly.

Disabled Postback

When fraudulent events are detected by the configured rules, it acknowledges the attribution for touchpoints or conversions, but postback will not be sent to channels.

Disabled Attribution

When fraudulent events are detected by the configured rules, it neither acknowledges attribution nor sends postback to the channels.

Was this article helpful?
0 out of 0 found this helpful
Current Page