Device Conflict protection and Report

AD Fraud : Device Conflict

With adbrix, you can acquire user device information on the time when a user reacts to the advertisement(impression, click, etc.) and when a user opens the application. ‘Device Conflict’ is a feature which uses two information acquired on each time to compare whether to see if the device information conflicts or not. Most of the cases for normal users show identical information for each time spot. However, for the AD Fraud which generates fake traffics for each spot has a high possibility of having different device information for each spot. 

‘Device Conflict’ distinguishes AD Fraud at ad-touch point and app open point based on the following information. 

• Model - Name of Device Model(e.g. iPhone 9, iPhone 10, SM-N960N, SM-G977N)
• OS - OS Version(e.g. iPhone 9, iPhone 10, SM-N960N, SM-G977N)
• Country (IP) - Country Information (IP Address based)(e.g. KR, JP, VM, US, UK)

Fraud Kill-Chain : Device Conflict

1. Defense conflict between the ‘device model name’ and ‘OS Version’ information collected on ad-touch point and app open point 

     - Also defenses when the ‘device model name’ and ‘OS Version’ is unknown.

2. Defense conflict between the ‘Country(IP based)’ information collected on ad-touch point and app open point. 

     - Also defenses when the ‘Country(IP based)’ is unknown.

3. Defense conflict between the ‘device model name’ and ‘Resolution’ collected on ad-touch point and app open point. (Coming soon)

Fraud Kill-Chain Setting

1) Default setting : Recommended

• The traffic in question is classified as Ad Fraud (or Organic) and is not included in the attribution report.
  
• The corresponding traffic is not postback to the media.
• You can check the scale of the corresponding traffic in the Fraud Index report

2) Included in attribution, but excluded from postback.

• The corresponding traffic is classified as a partner's success and included in the attribution report.
• This traffic is classified as Partner performance, but it is not posted back to the media partner (causing discrepancies between the console report and the media partner report).
• You can check the scale of the corresponding traffic in the Fraud Index report.

  3) Included in attribution and postback is sent (without any specific reason)

• The corresponding traffic is classified as partner performance and included in the attribution report
• The corresponding traffic is classified as partner performance and included in the attribution report, but the reason for fraud is not sent to the media through postback.
• You can check the scale of the corresponding traffic in the Fraud Index report.
   

 4 ) Include in attribution and send a postback with a reason

• The corresponding traffic is included in the attribution report and classified as partner performance.
• The corresponding traffic is postback to the media with the Ad Fraud ({blocking_reason} macro integration media included) reason included.
• You can check the scale of the relevant traffic in the Fraud Index report.
   

Check Reports

The traffic controlled by ‘Traffic Control’ can be checked in the ‘Single Touch Attribution’ report’s following metric.