Clear violations of platform billing terms flagged with supporting evidence for refund requests (e.g. via Google Ads credits).
Suspicious patterns that violate campaign intent or performance goals, flagged early to guide real-time blocking or bid reduction.
Core Standards
What We Look For
Clicks from known bot signatures, data‑center IPs, or abnormal click frequency.
• IP / UA matches known bot list
• ≥ 20 clicks from same IP in ≤ 10 s
• ≥ 100 clicks from same IP in 24 h
Eliminates non‑human traffic that never converts.
Standard
Google Ads Help – Invalid clicks definition (automated tools or robots) (support.google.com); MRC IVT 2.0 – GIVT Data‑Center Traffic (mediaratingcouncil.org)
What We Look For
Clicks from countries or regions outside your targeted geography.
• IP country = any location in the campaign’s exclusion list → Invalid
• IP in a non targeted location but have presence or interest ticked → Suspicious
Prevents spend on audiences you cannot serve.
Standard
Google Ads Help – Managing invalid traffic (location‑targeting discrepancies) (support.google.com)
What We Look For
Bursts of clicks outside campaign schedule or human‑like patterns (e.g., 50 clicks in 5 s).
Flags scripted click farms.
Standard
Google Ads Help – Invalid clicks (manual or automated click bursts) (support.google.com); MRC IVT 2.0 – Click Flooding (mediaratingcouncil.org)
What We Look For
Sessions with 0 s dwell time or immediate bounce, often tied to fake referrers.
1. For each campaign type, compute Bounce Rate = Bounce Clicks / Audited Clicks
2. Compare that rate to the table found here (https://help.blokid.com/audit-rules-traffic-classification?hsLang=en) :
• If Bounce Rate > Refund threshold
→ Invalid Traffic every incremental click:
(BR – Refund %) × CPC × Bounce Clicks
• Else if Bounce Rate > Over-charge threshold
→ Suspicious Traffic amount is
(BR – Overcharge %) × CPC × Bounce Clicks
Indicates no real user engagement.
Standard
Google Ads Help – Accidental clicks (no value to advertiser) (google.com)
What We Look For
Device reported by the ad platform ≠ device detected on your site.
Compare device string reported by ad platform vs. device detected on site
• Platform = mobile but onsite JS says desktop (or vice-versa) → Suspicious
• Emulator / spoofed user-agent detected → Invalid
Detects spoofed devices & emulators.
Standard
MRC IVT 2.0 – Device / Environment mismatch category (support.google.com)
We match your ad invoices to actual delivery. This detects inflated CPMs/CPCs, unserved ads, and billing discrepancies, helping you uncover hidden overcharges and reclaim lost spend.
We identify bots, click farms, and irrelevant placements. This allows your team to flag low-quality traffic sources, refine campaign targeting, and protect your media budget moving forward to save costs up to 30% each month.
Ensure your ads are only shown in your intended regions. We flag misaligned impressions and clicks outside your geo-targeting, which reveals waste you didn’t know existed.
Receive dispute-ready documentation for reclaiming overspend. We package the audit findings into reports that support a strong case for Google and Meta refund claims.
.svg)
