What to demand a media buyer prove about invalid traffic
Meta and Google filter invalid traffic on their own inventory, but filtering is not proof. The clause, the three monthly numbers and the keep-cap-cut rule.
A platform's invalid-traffic filter answers one narrow question: will you be charged for this click. It does not answer the question you are actually spending money on — whether a human being saw your ad and acted on it. Filtration is a seller-side process, run against the seller's own definitions, adjudicated by the seller, credited at the seller's discretion. That is not a scandal; it is how walled gardens are built. It does mean your protection is not a better dashboard. It is a paragraph in the scope of work naming what must be proven, by whom, on what clock, and what happens when it is not proven. This article is that paragraph, plus the three numbers that make it enforceable.
What the seller is obliged to do — and only that
Start with what the platforms themselves put in writing: more specific than agencies assume, narrower than advertisers expect.
Meta publishes a description of methodology for its Facebook Feed, In-stream, right-hand column and Reels impressions, prepared under its ongoing Media Rating Council accreditation. Three sentences in it do the commercial work. On Facebook, Meta is "both the 'publisher' and 'ad server'" — there is no independent ad server in the chain to disagree with it. Its decision rate, its ability to collect enough information to make an invalid-traffic determination on Facebook and Instagram traffic, it states as 100%. It filters against external lists — the IAB spiders and robots list, the TAG data-centre IP list — plus its own machine learning and human review, with appeals available. And it recognises two kinds of invalid click: clicks that do not indicate genuine interest (repetitive or accidental clicks, clicks from Facebook itself), and clicks produced by prohibited means (fake accounts, bots, scrapers, browser add-ons). When suspicious activity is detected or reported, "a manual review is performed to determine the nature of the activity. You will not be charged for clicks that are determined to be invalid."
Google's documentation matters more to a buyer because it names the four categories it defends against — non-human traffic, accidental clicks, fraudulent placements such as clickjacking and ad stacking, and other invalid user activity including competitors clicking to burn your budget — and then names the remedy. Traffic found before the end of the billing cycle is removed from metrics and billing, and Google states plainly that no refund is necessary because you were never billed for it. Found after invoicing, you get a credit, "where appropriate and possible." Google also exposes a formal path most advertisers never use: you can request an investigation into possible invalid traffic.
Read those two documents side by side and the shape of your protection is clear: the platform will remove what it can prove, on its own definitions, before or shortly after billing, and it will issue a credit rather than a refund. Everything beyond that requires you to ask.
Filtration and verification are two different jobs
The distinction that belongs in every media agreement is between filtration and verification. The Media Rating Council's framework, adopted with the IAB, splits invalid traffic into general invalid traffic (GIVT) — known bots, crawlers, data-centre traffic, things on published lists — and sophisticated invalid traffic (SIVT) — activity that needs advanced analytics, multi-point corroboration and human judgement to identify. Filtration is good at the first category and improving on the second. Verification is an independent party applying its own accredited methodology to the impressions it can observe and reporting the result separately from the seller.
That independence is the whole value, and it is exactly what walled gardens restrict. The pattern to watch is not whether a platform offers third-party verification — several now do — but what the announcement puts in scope. When DoubleVerify announced independent measurement on TikTok's Pangle network in August 2026 across 48 markets, the named capabilities were brand suitability insights, video viewability and reporting. Fraud and invalid-traffic detection was not named. Display viewability was not named. Pre-bid controls were not named; the coverage was post-campaign. A press release can be true and still not cover your question, and the same discipline applies to a media report: ask which metric, on which surface, in which direction.
So the honest position for an advertiser on social platforms is that independent measurement exists but is partial and surface-specific. Which makes the commercial question "do you verify?" the wrong one. The right one is: which of my placements are measured by someone who is not the seller, and on which metrics?
The claim, the measurer, and what you can actually require
| The claim in your report | Who measures it | What the platform will do about it | What to ask for monthly |
|---|---|---|---|
| "Meta filtered invalid impressions" | Meta, against its own MRC-accredited methodology | Removed from reporting before billing — no auditable line item | The methodology document your account is billed under, plus any filtered-volume figure Meta discloses for the period |
| "Clicks were removed as invalid" | Meta, by manual review after detection or an alert | You are not charged for clicks determined invalid — a credit, not a refund | The credit rows in billing transactions for the period, with the date they were applied |
| "Google filtered invalid traffic" | Google's ad traffic quality team — automated filters, machine learning, manual review | Removed from metrics and billing before the cycle ends; Google states no refund is necessary | The Invalid activity credit rows, or an explicit "none this period" |
| "Suspicious activity found after billing" | Google, only after you file | A billing adjustment — a credit, where appropriate and possible | Every investigation request filed, its date and its outcome |
| "Your ads ran in suitable apps" | A third-party vendor, on named surfaces only | Nothing — measurement is not a credit mechanism | Which surfaces are covered, which metrics are in scope, and whether invalid traffic is one of them |
The last row is the one agencies skip. A verification badge in a deck is not an invalid-traffic measurement unless invalid traffic is explicitly listed as an in-scope metric on your placement.
The clause to paste into a scope of work
Traffic quality. Platform-side invalid-traffic filtration is a seller-side process and does not constitute independent verification. Within ten business days of each invoice, the vendor shall report, per platform: (a) any invalid-activity credit or billing adjustment applied to that period's spend, with amount and date; (b) the status of every invalid-traffic investigation request filed during the period, with filing date and outcome; and (c) the share of total spend delivered on placements carrying no independent third-party measurement coverage. The vendor shall file an invalid-traffic investigation with the applicable platform within five business days of a written request from the buyer, and shall forward any resulting credit to the buyer. Any figure a platform declines to state in writing shall be recorded as self-reported. Nothing in this clause obliges either party to treat a platform-reported number as an audited figure.
It is short on purpose. Contracts that survive contact with a busy month are the ones a vendor can answer in an afternoon without a data request.
Three numbers, every month
- Credits booked. Every invalid-activity credit or billing adjustment applied in the period, by platform, with the date. If the answer is none, the report should say none — silence is the failure mode, because a missing line reads as a healthy account.
- Investigations filed and closed. Which requests went in, when, and what came back. This is the number that separates a vendor who watches the account from one who reports on it: an agency that has never filed an investigation on a year of spend has never checked whether the platform would answer.
- Self-reported share of spend. The percentage of budget delivered on placements nobody independent measures. This is the only one of the three that is a risk figure rather than an outcome figure, and the one worth watching across a quarter.
Notice what is absent: a percentage of your traffic that is fraudulent. Nobody can give you that number honestly, and any vendor who quotes it to three significant figures is selling detection. All three numbers above come from billing records and a written answer — which is exactly why they belong in a contract rather than a dashboard.
Keep, cap, or cut
- Keep. A credit appears or an investigation closes clean, and your destination-side check holds — platform-reported clicks still reconcile against the sessions your analytics records for the same period. Traffic quality is not your constraint; go back to creative and offer.
- Cap. The platform reports and credits nothing, but your destination-side numbers are stable and lead quality holds. Cap the affected placement's budget share until the vendor produces the disclosure. You are not punishing the platform; you are pricing unverified inventory.
- Cut. The gap between platform clicks and landed sessions widens while the vendor will not or cannot file, or a material share of spend sits on self-reported-only placements with no path to disclosure. Move the budget. This is the same divergence logic we use in the four-check diagnosis for Meta accounts, applied at the contract level rather than the account level.
The diagnostic tells you whether you have a traffic-quality problem. This clause decides who pays for it. They are two halves of one control — and the second half has to be signed before the invoice.
Where this sits next to conversion counting
Invalid traffic is a delivery problem, platform-reported conversions against your CRM is a counting problem, and the event setup that feeds both is a configuration problem — three failures that never announce each other. Settle them in that order before you read a cost per lead.
The direct answer
What you can demand a media buyer prove is narrower than what you would like and wider than most reports disclose: that the platform's own filtration was applied under its published methodology, that every credit it owes has been booked, that every investigation you are entitled to has actually been filed, and that the share of your spend nobody independent measures is a stated number rather than an unstated one. Filtration proves you were not charged for what the seller could see. Verification proves something else entirely. Your scope of work should say which one you are buying.
If you want that clause reviewed against an existing agreement, or the three numbers built into a monthly report from the start, it is part of how we run digital ads and PPC management — and the fastest next step is a working session on your account.
Frequently Asked Questions
Does Meta or Google refund invalid clicks?
Neither issues a cash refund as of right. Google removes invalid traffic it finds before the end of the billing cycle from both metrics and billing, and states that no refund is necessary; anything found after invoicing is settled as a billing adjustment, a credit, where appropriate and possible. Meta states that you will not be charged for clicks determined to be invalid, which again lands as a charge removed or credited rather than money returned. Both outcomes are seller-side determinations — you can file an investigation, but you cannot compel an independent audit from inside the platform.
Can a small advertiser run third-party verification at all?
On open-web and programmatic placements, yes — verification vendors sell pre-bid and post-bid measurement at campaign level and the minimums are not enterprise-only. On walled-garden social the answer is narrower: coverage exists but is surface by surface, metric by metric, and some of it is post-campaign rather than pre-bid. A small advertiser's better first move is the disclosure clause below: make the vendor state which placements are independently measured and which are self-reported, then buy verification only for the inventory that actually moves budget.
What belongs in a monthly traffic-quality report?
Three lines, not three paragraphs. One: every invalid-activity credit or billing adjustment applied in the period, with platform, amount and date. Two: every invalid-traffic investigation request filed, with filing date and outcome. Three: the share of spend delivered on placements with no independent third-party measurement coverage. If a vendor cannot produce those three lines, the traffic-quality section of the report is an assertion, not a measurement.
