Check Traffic Control settings and reports

Ad Fraud: Unintended Traffic

There are cases where traffic of types excluded from the advertising target is recognized as advertising performance and flows into the app. For example, if the targeting option for Korea is set within the advertising partners platform (or the advertiser requests the partner), but users from countries other than Korea are coming in.This case is called Unintended Paid User Acquisition . In another example, in a situation where fraudulent traffic inflow from a specific sub-publisher is suspected, the De-Targeting option is set within the partner company's platform (or the advertiser requests the partner company), but traffic continues to flow in. There is also. Even in this case, unintended users are introduced through advertisements.

Traffic Control Setting Items

Fraud Kill-Chain provides a Traffic Control function so that traffic types that cannot be controlled at the partner level can be controlled through the Traffic Control function. The factors that can be controlled through the Traffic Control function are as follows.

- Ad Touch: Traffic is controlled based on user information obtained at the ad touch stage.

- Event: Traffic is controlled based on user information obtained during the open and in-app event stages.

How to set up

1) Activate the toggle.
2) Click the +Add button to add detailed analysis conditions .
3) elements (eg. Platform, Country, etc.).
4) Select whether to include or not include .
- Included: If it is not included in the detailed elements set, it is considered a blocking reason and traffic is controlled.
- Not included: If included in the detailed elements set, it is considered a blocking reason and traffic is controlled.
5) Select the detailed element value (multiple selections are possible.)
6) Press the edit button at the bottom right to save the settings.

[[Quote:Guide:Small]] I can't check the detailed element values!

- If SDK integration is recent, detailed element values ​​may not be confirmed.
- If it is a detailed element value that can be entered directly, it can be set in a way that reflects the keyword.

Setting example

The reason for blocking is interpreted based on the directly set example screen and applied to the actual settings.
All examples described are subject to the global terms of exclusion from attribution and no postbacks .

Setting example #1.

1. Among the data obtained from events (open and in-app events), if the platform information is Android and the IP-based Country information is JP:
>> Platform information is Android, but Country information is JP, not KR, which is set to be included. It is controlled as a blocking reason.

2. Among the data obtained from events (open and in-app events), if the platform information is iOS and the IP-based Country information is KR:
>> Country information is KR, but since Platform information is iOS, not Android, which is set to include, it is considered a blocking reason and is controlled.

3. Among the data obtained from events (open and in-app events), if the platform information is Android and the IP-based Country information is KR:
>> We judge you to be a normal user .

[[Quote:Warning:small]] Be sure to check it out!

- If multiple detailed conditions are set, it operates as an AND condition in which each condition must be met.
- Adtouch and event items independently control traffic at the user ad participation stage and app inflow stage.

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.