Display Ad Server
Serve ads in standard fixed-size ad units
Native Ad Server
Serve native ads on your web page or app
Video Ad Server
Serve MP4 video ads as pre/mid/post-rolls
For Publishers
Maximize revenue for direct deals.
For Advertisers
Optimize campaigns, real-time insights.
User GuideAPISupport

Bot Filter


AdGlare has a built-in bot filter to detect crawlers and spiders. As we're living in a world where about half of the internet's traffic is caused by bots, it's important to filter them in order to avoid skewing your reports.

Type of bots

Two types of bots can be detected: GIVT (General Invalid Traffic) and SIVT (Sophisticated Invalid Traffic).
  • GIVT traffic is detected by analyzing the user-agent string. For example, Googlebot, AHrefs Bot and PageSpeed bots all have a user-agent string that shows who they are. By matching the user-agent string against a list of known bots, GIVT traffic can be detected.
  • SIVT traffic refers to more advanced forms of invalid traffic. It requires more sophisticated methods to detect and filter such bots, as they intentionally present themselves as human traffic. This may be a warning sign of fraudulent activity. To not make fraudsters wiser than they are, I won't disclose AdGlare's algorithms used to detect SIVT traffic here.

Filtering bot traffic

By default, ads will be shown to bots. Their impressions and clicks will be counted. You can generate a Non-Human Traffic report to see the number of events that were logged by bot traffic. If you're a publisher, you can adjust the invoice for your advertiser accordingly by not charging for bot traffic.

Alternative, you can filter bot traffic from your reports as soon as event data is sent to your ad server. Bot traffic still load ads, but their impressions and clicks will simply be discarded before it hits the report cluster. The advantage is that your reports are much cleaner as bot traffic is not included in your metrics.