MOAT Invalid Traffic (IVT)

Invalid traffic (IVT) reporting includes a number of fields that provide metrics on invalid (‘non-human’) impressions delivered.

Invalid traffic reporting is currently available for creatives with MOAT viewability tracking implemented. Metrics can be found in the performance report and inventory report in query tool. Please note that Invalid Traffic reporting is only available on traffic served in a web environment.  

The below creative template/MOAT integration combinations will provide invalid traffic reporting:

Creative Template How to Implement
VAST 2.0 Inline Select “MOAT Web Viewability” under “Creative Attributes” in the Edit Creative screen
VAST 2.0 Wrapper with MOAT Viewability No additional action needed when using this template
Any Banner Template Select MOAT Banner Tag under creative add-on

Below are the available invalid traffic metrics/fields in reporting (available in performance & inventory reports):
Name Metric or Field Description
Invalid Impressions Metric Number of Invalid Impressions as measured by MOAT
Measureable Invalid Impressions Metric Number of Impressions that were Measurable for Invalid Impressions by MOAT
Invalid Imp % Metric Invalid Impressions / Impressions
Invalid Impression Reason Code Field There are three reason codes:
Automated Browser Data Center Traffic

Incongruous Browser

Measurement Vendor Name Field The vendor used to measure, in this case “MOAT”

Reason Codes Definitions (as defined by MOAT)

MOAT defines three reason codes for why an impression was tracked as Invalid

  • Automated Browser: Impressions determined to originate from an automated browser
  • Incongruous Browser: Impressions determined to originate from a browser with an incongruous feature set
  • Data Center Traffic: Impressions determined to originate from a data center

Standard MOAT pricing applies and is listed in the Beeswax user interface. Please note these fields will not be available in any logs.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us