Skip to answers
Knowledge BaseTraffic quality & conversion answersTechnical documentation ↗
Browse answers

Traffic Detective

What counts as invalid traffic (IVT)?

In short

IVT concerns advertising interactions that should not be treated as valid. Automated traffic and paid-click IVT overlap, but not every crawler request is an invalid paid click.

Research context

The Media Rating Council defines IVT as activity unsuitable for legitimate measurement counts and distinguishes general from sophisticated invalid traffic (GIVT/SIVT). Google Ads applies its own detection and billing treatment; a suspicious site visit is not automatically a billable invalid click.

GIVT - General Invalid Traffic

Key examples are:

• Known invalid data-center traffic (determined to be a consistent source of invalid traffic; not including routing artifacts of legitimate users or virtual machine legitimate browsing);

• Bots and spiders or other crawlers (except those as noted below in the “Sophisticated Invalid Traffic” category);

• Activity-based filtration using transaction-level data and parameters from campaign or application data;

• Non-browser user-agent headers or other forms of unknown browsers;

• Pre-fetch or browser pre-rendered traffic (where associated ads were not subsequently accessed by a valid user; note: updated IAB/MRC Measurement Guidelines require an ad to have loaded and begun to render in order to record an impression; as a result, pre- fetch or pre-rendered traffic shall not be included in Gross impression counts );

• Invalid placements (specific to ads); small, barely visible or invisible ad delivery or illogical (non-industry standard) ad size of: 0x0 and 1x1 as delivered on the client side (Note: When using declared ad sizes, efforts should be made to determine whether bid request declarations are for request purposes only or represent actual placement size);

• Non-rendering capabilities; sessions or traffic without the capability to render or display images (other than cases of disabled image rendering) as determined at the client side even though rendered impressions or other activity may be associated with them such as headless browsers or component devices without a display component. To be clear, this required GIVT category relates to measured activity (such as rendered impressions) associated to sessions where device information appears incapable of or illogical with rendering ability. Non-rendered impressions should continue to be omitted from Gross Impression measurement and not treated as IVT.

Common ways to filter the more obviously invalid traffic are checking user-agent strings, checking the visitor's IP ranges and checking request parameters.

Non-rendering browsers are almost always invalid, except for ad verification bots (which use published IP ranges and a specific user agent). That's why we don't recommend adding a static "pixel" just to detect them. If you need it, we're happy to add support.

SIVT - Sophisticated Invalid Traffic

• Automated browsing from a dedicated device: Known automation systems (e.g., monitoring/testing), emulators, custom automation software and tools;

• Automated browsing from a non-dedicated device: infected and hijacked devices (and sessions within) as well as incentivized automated activity;

• Incentivized human invalid activity: self-directed activity to benefit self or harm others and directed activity;

• Manipulated activity: Forced new browser window opening, forced tab opening, forced mobile application install (mobile re-direct), forced clicking behavior, tricking users to click / accidental clicks, clickjacking (UI redress attack) and hijacked measurement events;

• Falsified measurement events: visit, impression, viewability, click, location (specific to location falsification aimed at generating invalid ad activity, but not necessarily including validation of exact location for targeting purposes), referrer, consent string, conversion attribution and user attribute spoofing as well as Server Side Ad Insertion (SSAI) spoofing where applicable to a measurement organization;

• Domain and App misrepresentation: App ID spoofing, domain laundering and falsified domain / site location;

• Bots and spiders or other crawlers masquerading as legitimate users detected via sophisticated means;

• Hijacked ad tags and creatives (specific to ads);

• Hidden/stacked/covered/transparent/invisible or otherwise intentionally obfuscated ad serving such as Z-order stacking, banner stuffing, transparent ads and background cycling and pop-under with auto-close (specific to ads);

• Invalid proxy traffic (originating from an intermediary proxy device that exists to manipulate traffic counts or create/pass-on invalid traffic or otherwise failing to meet protocol validation);

• Adware and Malware that conduct deceptive actions including ad injection and unauthorized overlays;

• Incentivized manipulation of measurement (invalid incentivized promotion of an entity, without its knowledge or permission such as shilling or for purposes of manipulating measurement – excludes cases where the entity paying for the incentive is the entity being promoted);

• Misappropriated (pirated or stolen) content (where used to purposefully falsify traffic at a material level);

• Cookie stuffing, recycling or harvesting (inserting, deleting or misattributing cookies thereby manipulating or falsifying prior activity of users); and

• Differentiating valid and IVT traffic when originating from the same or similar source in certain closely intermingled circumstances

This is where it gets really interesting.

For instance, Google's SearchGuard tests a large number of parameters.

While the technical foundation of SearchGuard, BotGuard (created by Mike Hearn), is very solid, the tests we found when we examined SearchGuard were significantly sparser than those used for Google Login.

Everything is a tradeoff. Part of the reason SearchGuard can do less is that Google also has Chrome, with its X-Client-Data and special headers.

So Google doesn't need to test directly whether a visitor is legitimate: a long stream of collected data often makes it clear.

Click-fraud solutions such as button ^ solutions don't have that history. We have to research more deeply to establish, in under a second, what an ad provider with analytics tracking can work out through side channels over days or weeks.

That research is what Smart Responder acts on: Button's own classification, built from different signals than the ones your ad provider collects.

Next step: Why did Button flag this visitor? · Related guide: Investigate invalid traffic and request credits using evidence

Sources and further reading

Button Solutions Knowledge Base Evidence before action.