Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

IVT Data

Benefits of using IVT Data

IVT Metrics show the amount of "invalid" traffic coming through your account measured by different vendors. These metrics are extremely useful for creating blacklists to block domains with a high frequency of "invalid" traffic. 

Even with Pre-Bid IVT Blocking enabled on a supply tag, we highly recommended utilizing post-impression detection along with tag health flags. Pre-Bid IVT blocking takes place at the request level, and is not guaranteed to detect and block all IVT at that stage. Post-Imp IVT data is collected and analyzed at the impression level, and thus will be able to catch IVT traffic that other detection methods will not. 

Best Practices

Moat data is delayed by 3 to 9 hours, and IAS data is delayed by 12-36 hours. Moat and IAS metrics will show as zero until the data has been populated. Run a report with Moat Bot % and IAS IVT% to see which of your tags recently had a high bot/IVT rate.

...

It is highly recommended that you run this bot analysis regularly, not only when your general bot rates are high. 

Back to top


SpringServe Suspected IVT Daily Alert:

This alert includes supply tags whose traffic for over the last 24 hours had key signatures of invalid traffic. This was determined from internal IVT detection measures. These tags should be cleaned up or paused, otherwise discrepancies and future clawbacks are at high risk of happening.
The table in this report contains two metrics: measurable rate and SIVT rate. Measurable Rate indicates the percentage of impressions that were able to be evaluated for IVT. Impressions that are not able to be analyzed are often invalid, so having a very low measurable rate is also a red flag for IVT. SIVT Rate is the percentage of analyzed impressions that were found to be invalid.

If you have further questions, go to FAQ or contact support@springserve.com