Traffic Control Setting and Reporting

AD Fraud : Uninteded Traffic

Sometimes, types of traffic which have been excluded from the campaign target get recognized as campaign performance and flow into the service. For example, although the target country of the campaign inteded was ‘Japan’ the actual users acquired are from other countries than Japan. This case is called ‘Uninteded Paid User Acquisition’. Another example can be the case even though you have de-targeted certain sub-publisher’s traffic because that sub-publisher seemed like generating fraud traffic, but you still receive traffic from the sub-publisher. All these cases are included in the category of ‘Unintended Paid User Acquisition’ fraud.

Traffic Control Setting

Fraud Kill-Chain provides ‘Traffic Control’ feature which enables you to control the types of traffic you receive from the ad partners. The factors you can control with ‘Traffic Control’ feature is as following. 

 - AD Touch: Control the traffic based on the user information collected on the ad-touch level.

- Event: Control the traffic based on the user information collected on the open & in-app event level.  

How to Set?

   1) Activate the toggle.
   2) Click +Add button to add detailed conditions for the analysis.
   3) Choose Factor(eg. Platform, Country, etc.).
   4) Choose whether to include or exclude.

       - Include : Report as fraud if the user information does not match with the condition. 
       - Exclude : Report as fraud if the user information matches with the condition. 

   5) Choose detailed conditions for the factor. (You can choose multiple factors.)
   6) Save by clicking the ‘Update’ button at the bottom right corner.

[[인용:정보:작게]]I can’t see the sub-conditions!

- If the SDK integration is recent, the sub-conditions might not yet be updated.
- If the value can be directly filled in, you can try to set it by applying keywords.

Example Setting

Take a look at the example screen, and let us see how the traffic is blocked and it can be set.

All the example elaborated follows the global condition which excludes from attribution and does not send post-back. 

Example #1.

1. If the data collected from the ad-touch(Click, Impression) tells the information of platform is ‘Android’, and Region(IP) is ‘Tokyo’:

    >> ‘Exclude’ condition ‘Tokyo’ is included in the information collected, so this will be regarded as ‘fraud’.

2. If the data collected from the ad-touch(Click, Impression) tells the information of platform is ‘iOS’, and Region(IP) is ‘Seoul’:

   >> Although the region information is not ‘Tokyo’, but the platform information is iOS, not ‘Android’, the traffic will be regarded as ‘fraud’. 

3. If the data collected from the ad-touch(Click, Impression) tells the information of platform is ‘Android’ and Region(IP) is ‘Seoul’:

   >> Regards as legitimate user.

Example #2.

1. If the data collected from the event(open & in-app events) tells the information of platform is ‘Android’ and Country(IP) is ‘Japan(JP)’:

    >> Although ‘Platform’ information is ‘Android’, the ‘Country’ information is not ‘KR’ which is set to be ‘included’, but ‘JP’, the traffic will be regarded as ‘fraud’. 

2. If the data collected from the event(open & in-app events) tells the information of platform is ‘iOS’ and Country(IP) is ‘Korea(KR)’:

   >> Although ‘Country’ information is ‘KR’, the ‘Platform’ information is not ‘Android’ which is set to be ‘included’, but ‘iOS’, the traffic will be regarded as ‘fraud’. 

3. If the data collected from the event(open & in-app events) tells the information of platform is ‘Android’ and Country(IP) is ‘Korea(KR)’:

  >> Regards as legitimate user.

[[인용:경고:작게]] Please be noted!

- If you have set multiple sub-conditions, the system will run with AND condition which requires all the conditions to be met.
- Ad-touch and event options each independently controls the traffic of user acquisition steps and advertisement participation steps.

Fraud Kill-Chain Global Setting

1) Default Setting : Recommended

 - Traffics are not included in the attribution report and classified as AD Fraud(Or organic)
 - Traffics(post-back) are not sent to AD Partners.
 - Traffics can be checked in the Fraud Index report. 

2) Include in the attribution, and send post-back

 - Traffics will be included in the attribution report and classified as AD Partner’s credit.
 - Traffics(post-back) are not sent to AD Partners. (Console report and media report will have some discrepancies.)
 - Traffics can be checked in the Fraud Index report.

  3) Include in the attribution and send post-back(without reason).

 - Traffics will be included in the attribution report and classified as AD Partner’s credit.
 - Traffics(post-back) will be sent to AD Partners without reason.
 - Traffics can be checked in the Fraud Index report.

 4 ) Include in the attribution and send post-back(with reason)

 - Traffics will be included in the attribution report and classified as AD Partner’s credit.
 - Traffics(post-back) will be sent to AD Partners with reason. (only to the media which integrated {blocking_reason}  macro.)
 - Traffics can be checked 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 categories.