The MRC-standard category for routinely identifiable invalid traffic — declared crawlers, data-center IPs, known-bot lists — removable by standard filtration before numbers are reported.

How does GIVT differ from SIVT?

GIVT announces itself or matches lists; SIVT is engineered to look human — hijacked devices, residential proxies, the fraud schemes requiring forensic analytics rather than list checks.

What should buyers verify about IVT filtering?

Which lists, applied at which pipeline stage, accredited by whom — and whether SIVT detection exists separately, because clean-GIVT reporting only proves the polite bots are gone.

Growth Marketing Glossary

General Invalid Traffic (GIVT)

G·I·V·Tnoun

The bots that announce themselves — filtered by list, reported by standard, and dangerous mainly when mistaken for the whole problem.

Schematic — the self-announcing half of invalid traffic

Term: General Invalid Traffic
From: MRC invalid-traffic standards
Caught by: Lists — IAB bots, data centers, agents
The trap: Clean GIVT read as clean traffic

Forms & parts of speech

GIVT · noun

List-filterable invalid traffic.

"GIVT filtration caught the declared crawlers - the budget's real leak was the SIVT designed to pass exactly that filter."

Definition in plain terms

General invalid traffic (GIVT) is the ad industry's category for non-human traffic that identifies itself or matches known lists: declared crawlers (GOOGLEBOT announcing its name honestly), data-center IP ranges, known-bot user agents, and pre-fetch activity. The term comes from the MRC's invalid-traffic standards, which split the problem in two — GIVT, removable by routine list-and-parameter checks, and SIVT (sophisticated invalid traffic), the disguised fraud requiring forensic analytics — a split that exists precisely because filtering the polite bots says nothing about the impolite ones.

The mechanics

The filtration is genuinely routine: the IAB/ABC international spiders-and-bots list matches declared agents, data-center ranges flag traffic from racks where no humans browse, and self-declared automation (monitoring tools, the pre-render fetches) subtracts cleanly — which is why GIVT filtration is table stakes in any MRC-accredited measurement, applied before reported numbers reach you. What lives in each bucket matters operationally: GIVT is mostly honest infrastructure (search crawlers, uptime monitors, the AI-era crawler wave swelling the category) plus lazy fraud that never bothered to hide; SIVT is the engineered remainder — the CLICK-INJECTION and CLICK-SPAMMING entries' schemes, DOMAIN-SPOOFING's laundered inventory, hijacked devices, and the BOT-TRAFFIC that rotates residential IPs specifically to fail list-matching. The trap the split exists to prevent: 'IVT-filtered' reporting read as 'fraud-free' reporting — GIVT removal is hygiene, not verification, and a buyer who stops at it has filtered exactly the traffic that wasn't trying. The practical stack: GIVT filtration assumed (and audited — ask vendors WHICH lists, applied WHERE in the pipeline), SIVT detection priced as the separate forensic product it is, and the fraud-fingerprint disciplines this glossary's fraud entries teach (timing distributions, render verification, supply-path audits) doing the work lists cannot.

When it matters

GIVT matters as the baseline every measurement contract should name — which lists, whose accreditation, applied pre- or post-billing — and as analytics hygiene beyond ads (the ENGAGED-SESSION entry's junk-traffic tells are often unfiltered GIVT polluting site metrics). It matters most as vocabulary precision in vendor conversations: 'we filter IVT' deserves the follow-up 'general, sophisticated, or both — and verified by whom?' The discipline is the split respected: lists for the polite bots, forensics for the engineered ones, and clean-GIVT reports never mistaken for clean traffic.

Worked example. A B2B publisher's traffic doubles in a quarter and the ad team celebrates until the sell-through math misbehaves - advertisers' engagement metrics on the 'grown' inventory crater. The IVT decomposition tells the story in layers: GIVT filtration (the IAB list + data-center ranges, applied properly for the first time) removes 18% of the 'growth' immediately - an uptime-monitor misconfiguration and the AI-crawler wave, honest bots inflating raw counts. The remaining anomaly fails the polite-bot lists entirely and needs the forensic layer: session-behavior analysis finds a purchased-traffic vendor delivering residential-proxy SIVT engineered to pass exactly the filters just installed. The cleanup runs both layers permanently - GIVT lists in the analytics AND ad-serving pipelines (named in the measurement contract, MRC-accredited verification on the premium inventory), the traffic vendor terminated with the forensic report attached, and reported inventory shrinking 24% to numbers that convert again. The lists caught what announced itself; the lesson was budgeting for what didn't.

Failure modes to watch. Reading 'IVT-filtered' as 'fraud-free' while SIVT is engineered to pass the lists; vendor contracts that say 'we filter bots' without naming lists, layers, or accreditation; analytics pipelines unfiltered while ad pipelines filter, leaving site metrics polluted; the AI-crawler wave inflating raw counts unsubtracted; and forensic SIVT detection unbudgeted because the hygiene layer felt like verification.

Synonyms & antonyms

Synonyms

general invalid trafficGIVTlist-filterable IVT

Antonyms

SIVT (the engineered remainder)valid human traffic

Origin & history

The GIVT/SIVT split comes from the MRC's invalid-traffic detection guidelines (2015 onward), which standardized what list-based filtration must remove and named the sophisticated remainder — a taxonomy that turned 'we filter bots' from a slogan into an auditable claim with accreditation attached.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is GIVT?: The MRC-standard category for routinely identifiable invalid traffic — declared crawlers, data-center IPs, known-bot lists — removable by standard filtration before numbers are reported.
How does GIVT differ from SIVT?: GIVT announces itself or matches lists; SIVT is engineered to look human — hijacked devices, residential proxies, the fraud schemes requiring forensic analytics rather than list checks.
What should buyers verify about IVT filtering?: Which lists, applied at which pipeline stage, accredited by whom — and whether SIVT detection exists separately, because clean-GIVT reporting only proves the polite bots are gone.

Related tools & calculators

toolCAC calculator
toolLTV:CAC calculator

Resources & people to follow

referenceMRC — invalid traffic standards and guidelines
referenceIAB/ABC international spiders & bots list documentation
referenceRGM analysis — lists for the polite bots, forensics for the engineered; hygiene is not verification

Curated, non-competitor resources verified per term.

Related training

modulePerformance marketing

Disciplines

Areas of marketing where general invalid traffic (givt) is a core concern:

Performance marketingGrowth strategy

Sources

trendsGoogle Trends — "invalid traffic"