Support Home > Campaign Management > Traffic Verifier

Traffic Verifier

 

The following document defines the process for setting up Traffic Verifier for a tracker within Kochava. Traffic Verifier is a real-time fraud mitigation tool for ensuring that only qualified traffic proceeds through the flow from impression to install. Various controls provide the tools to understand the effectiveness of marketing and provide a clear path to obtain traffic goals.

 

NOTE: Before Traffic Verifier settings can be set up, contact an account manager to enable the service.

 

Traffic Verifier enables Kochava users to perform tasks such as:

  • Establish rules to verify traffic in real-time.
  • Receive postbacks with violations of traffic rules.
  • If traffic violates rules, determine the actions taken with the invalid traffic.

Create a Traffic Verifier Configuration

  1. Log in to Kochava.
  2. Select App Tools>Campaign Manager.
  3.  

    AppToolsCampaignManagerHD

     

  4. Locate the desired Campaign and click the Campaign expand button.
  5. Locate the desired Tracker and select Tracker Tools>Traffic Verification.
  6.  

    A. Indicates that Traffic Verification has been set up on the Tracker.

     

  7. Click Status>ON.
  8.  

     

  9. Copy the rules from an existing Tracker. (optional)
  10.  

    A. Type Tracker name to search.

     

    NOTE: Once the settings from an Existing Tracker have been imported, the settings can be updated.


Determine Traffic Definitions

Filters:

  • Device>Platform
  • Device>OS Version
  • Device>Type
  • Geo>Country
  • Geo>City

 

BEST PRACTICES: It is recommended that you ONLY use Device Type filtering for trackers you know will be targeting in-app inventory.

 

NOTE: Filters are not active until a condition and value have been created.

 

Condition:

  • Matches
  • Doesn’t Match
  • Greater Than or Equal
  • Less Than or Equal

 

Values:

  • Specific Device Platform
  • Specific OS Version
  • Specific Device Type
  • Specific Country
  • Specific City

 

NOTE: The Values are dependant upon the filters selected. The list of values will update as different filters are selected.

 

BEST PRACTICES: It is recommended that a similar approach be used as the targeting criteria with Ad Network and Publishers. (i.e. using the “Matches” condition to identify the audience you are targeting)

 


Frequency Capping

Frequency Capping for traffic provides the tools for advertisers to balance reach vs. frequency. The frequency that Impressions and Clicks are verified may be capped by IP address, Site, Device ID or User Agent.

 

NOTE: Frequency Capping definitions use “AND” logic. Cap numbers will be applied to all Impression or Click definitions (e.g. IP AND Site AND Device ID).

 

Traffic

  • Impression
  • Click

 

Definition

  • IP
  • Site
  • Device ID
  • User Agent

 

Cap

  1. Enter a number to Cap the number of Impressions and/or Clicks.

 

Duration

  1. Select a Duration:
    • 1 min
    • 2 min
    • 3 min
    • 4 min
    • 5 min
    • 6 min
    • 7 min
    • 8 min
    • 9 min
    • 10 min
    • 15 min
    • 20 min
    • 25 min
    • 30 min
    • 35 min
    • 40 min
    • 45 min
    • 50 min
    • 55 min
    • 1 hr
    • 2 hr
    • 3 hr
    • 4 hr
    • 5 hr
    • 6 hr
    • 7 hr
    • 8 hr
    • 9 hr
    • 10 hr
    • 11 hr
    • 12 hr
    • 13 hr
    • 14 hr
    • 15 hr
    • 16 hr
    • 17 hr
    • 18 hr
    • 19 hr
    • 20 hr
    • 21 hr
    • 22 hr
    • 23 hr
    • 24 hr

Fraud Blacklist

Kochava provides access to our real-time Global Fraud Blacklist. Within Traffic Verifier, data associated with fraud may be filtered to provide the highest quality data possible.

 

IP

ON- All IP addresses associated with fraud will be filtered from the Traffic Verifier data.
OFF- All IP addresses will be included within the Traffic Verifier data.

 

Site

ON- All sites that are associated with fraud will be filtered from the Traffic Verifier data.
OFF- All site data will be included within the Traffic Verifier data.

 

Device ID

ON-All device IDs that are associated with fraud will be filtered from the Traffic Verifier data.
OFF-All Device IDs will be included within the Traffic Verifier data.

 

A. Select “ON” or “OFF”


Action for Invalid Traffic Actions

Invalid Traffic Metadata:

  • traffic_validated = false
  • invalid_traffic = click
  • traffic_rule = see below

 

Attribute:

ON- Will allow the invalid impression/click to be considered for install reconciliation matching and potentially be awarded attribution.

OFF- Will allow the invalid impression/click to be considered for install reconciliation matching but will NOT allow it to be awarded attribution.   It still can be identified as an influencer.

 

Deliver Network Postback:

ON- Will allow the delivery of the Postback to the Network awarded install attribution for the invalid traffic.

OFF- Will not allow the delivery of the Postback to the Network awarded install attribution for the invalid traffic.

 

NOTE: If you have custom postbacks configured, the postback still will be sent regardless of this ON/OFF.

 

  1. Click Save.

 

A. Select “ON” or “OFF”


Custom Advertiser Postback

NOTE: In order to add custom parameters to a Custom Advertiser Postback, contact your account manager.

 

Parameter Sample Values Description
traffic_validated success
failure
disabled
blank
Flag that describes whether or not the click met traffic verification rules. If traffic verifier was set for a tracker and then turned off, you will receive “disabled”. If it was never turned on you will receive a blank value
invalid_traffic 109310161 References the click ID that was flagged as invalid per the rules you set.
traffic_rule blacklist_ip
blacklist_site
blacklist_device
frequency_cap_click
frequency_cap_minutes
frequency_cap_imp
frequency_cap_click_definition
frequency_cap_imp_definition
city_in
city_not_in
dma_in
dma_not_in
postal_in
postal_not_in
state_in
state_not_in
country_in
country_not_in
device_type_in
device_type_not_in
device_version_in
device_version_not_in
os_version_in
os_version_not_in
os_version_greater_than
os_version_less_than
platform_in
platform_not_in
Describes the category of rule that caused the click to be flagged as invalid.
traffic_value 5.0 Describes the value received on the click that did not meet configured traffic verifier rules.

NOTE: For more information or further examples of traffic_value, contact your Account Management team.


Reporting

Reporting of Verification Traffic associated with Clicks and Impressions is available. For more information, refer to our Reports Overview or Pulling Reports support documentation.


Analytics

Traffic Verifier data is also ingested and may be displayed within Kochava Analytics. Analytics provides the ability to perform a split by either “Traffic Verified” or “Traffic Verification Fail Reason”.

 

Reason Codes Returned:

Traffic Verified –

  • Unknown
  • 1 (true)
  • 0 (false)

Traffic Verification Fail Reason –

  • Unknown
  • Null (a zero)
  • blacklist_site (Instance belongs to an identified fraudulent site)
  • blacklist_device (Instance belongs to an identified fraudulent device)

 
 

Last Modified: Dec 14, 2017 at 9:44 am