Page tree

Versions Compared


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


The reason why a duplicate demand tag would not perform the same if it is in the same waterfall as its clone, is because the demand tags will end up competing for the same requests, therefore the older and more established tag will end up eating up most of the requests.

IVT Troubleshooting

Which IVT vendors are available to use in SpringServe?

SpringServe offers a seamless plug-in for both Pre-bid and Post-Impression detection with various partners. Detection is available on both your supply and demand tags.


  • WhiteOps - Desktop, Mobile-web. Could be used for In-app traffic as well. 
  • Protected Media - Available for Desktop, Mobile-web, In-app traffic.  CTV is in beta. Please let your account manager know before activating.
  • SpringServe - Pre-bid based on specific things that SpringServe has come up. Not algorithm based.


  • WhiteOps
  • MOAT
  • IAS
  • Protected Media
  • Forensiq

How do I choose an IVT vendor?

SpringServe suggests sampling at least 20% from each post-imp IVT vendor. You could always change the sample rates to find the results you desire. You could also choose your vendor based on the environment of your tag. Protected Media is currently the only vendor available for CTV environments.

Which IVT vendor should I use based on the environment of my tags?

For Desktop and Mobile web all IVT vendors could be used. For In-app tags we recommend Forensiq and Protected Media and for CTV the only option is Protected Media.

What percentage of traffic should I validate?

In the 'Post-Imp Detection Components' section on the supply settings page you could apply 100% of your traffic to one IVT vendor or select a split sample for a total of 100% between any/all vendors. 

How do I select between pre-bid and Post-imp IVT detection?

Pre-bid verification analyzes the request before a bid is even made. It uses previously gathered data alongside real-time machine learning to determine if an ad should even be shown to a user.  Pre-bid IVT filtering is available on both supply and demand tags in SpringServe. Enabling pre-bid on a demand tag protects specific demand sources from IVT, so that you could reduce costs by not running it on your entire supply. Only requests that have been approved by the selected vendors will be passed to the demand tag.

Post-imp verification analyzes the request after the ad has already shown. It allows a user to see where the traffic sources come from and set their own blacklists and whitelists according to the data that is found in reports.

Pre-bid with a small sample of Post-imp provides the verification vendor with useful data to make the algorithm smarter.

How do I run an IVT report?

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. 

To see which tags have a high IVT percentage in reporting use the following IVT Metric selections respectively:

Image Added

Please note that the data depends on when our partners make the data available to us. If you see 'zeros' in reporting, it means thats SpringServe does not have the data yet. Data delays for each IVT partner are as follows:

  • White Ops - 7 hours
  • Moat - 3 to 9 hours
  • IAS - 12-36 hours
  • Forensiq - 1 full day/24 hours
  • Protected Media - 2 hours

If your tag has a high bot/IVT rate, run a new report with the time range set to Custom spanning 2-3 days, and add the dimension 'Declared Domain' for Desktop and Mobile web, and App Bundle or app name for In-app and CTV campaigns. You could then narrow down the results of the sources with high IVT rates and add them to new or existing blacklists.  This can be a blacklist for the tag specifically, for a supply partner, or a master blacklist for all of your tags, whatever your preference is. Make sure the blacklist is implemented in the tag's targeting. 

One thing to note when using Protected media for IVT detection is that GIVT, SIVT, and Suspicious traffic are all considered IVT in SpringServe so if your IVT rate seems excessively high please take this into account.  If you would like a further breakdown of traffic or have any questions feel free to reach out to product support.

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

Could I have access to the IVT vendors dashboard?

This is a special request that will be evaluated on an "as needed" basis. Please reach out to your account manager if you would like more information.

Why are my IVT numbers different across all vendors?