Check Device Conflict defense settings and reports

Ad Fraud: Device Conflict

DFINERY can secure user device information when a user reacts to an advertisement (impression, click, etc.) and when the user enters the app.Device Conflict is a method of controlling a case where device information obtained at two times conflicts by considering it as Ad Fraud. In the case of normal users, most of the information recorded when reacting to an advertisement (ad touch) and when entering the app matches. On the other hand, in the case of Ad Fraud, which creates data at each point in time with virtual traffic, there is a high possibility that device information at each point in time will be recorded differently.

Device Conflict determines Ad Fraud based on the data below at the time of ad touch and app installation.

• Model - Device model name ( eg iPhone 9, iPhone 10, SM-N960N, SM-G977N)
• OS - OS version ( eg iPhone 9, iPhone 10, SM-N960N, SM-G977N)
• Country (IP) - Country information (based on IP Address) ( eg KR, JP, VM, US, UK)
  

Fraud Kill-Chain: Device Conflict

1. Prevent device model name and OS version conflict between ad touch and installation
- It is also not allowed when the device model name and OS version are unknown.
2. Prevents national (IP-based) information conflict between ad touch and installation
- It is not allowed even when country (IP-based) information is unknown.
3. Defense when the device model name and standard resolution are different (service being prepared)

Apply Fraud Kill-Chain global settings

1) Default setting: Recommended setting method

- The corresponding traffic is not included in the attribution report and is classified as Ad Fraud (Or Organic).
- We do not post back the relevant traffic to the media company.
- You can check the corresponding traffic size in the Fraud Index report.

2) Included in attribution but excluded from postback

- The corresponding traffic is included in the attribution report and classified as partner performance.
- We do not post back the relevant traffic to the media company. (There is a numerical difference between the console report and the media company report)
- You can check the corresponding traffic size in the Fraud Index report.

3) Include in attribution and send postback (no reason)

- The corresponding traffic is included in the attribution report and classified as partner performance.
- The relevant traffic is posted back to the media company, but no reason for fraud is sent.
- You can check the corresponding traffic size in the Fraud Index report.

4 ) Include in attribution and send postback (including reason)

- The corresponding traffic is included in the attribution report and classified as partner performance.
- Post back the relevant traffic to the media company, including the reason for Ad Fraud ( {blocking_reason} macro-linked media only). - You can check the corresponding traffic size in the Fraud Index report. Macro-linked media only) Postback including reason.
- You can check the corresponding traffic size in the Fraud Index report.

Check the report

Traffic controlled by Traffic Control can be checked through the Metric items below in the Single Touch Attribution report.