How to filter bot traffic in Google Analytics 4 (GA4)

Updated 2026-06-17 · Editorial Team · 10 min read

Affiliate disclosure: some outbound links carry our partner tracking. Commission does not change rating. Disclosure.

Bot traffic is the silent killer of GA4 data quality. The default 'Exclude known bots and spiders' filter catches the obvious crawlers (Googlebot, Bingbot, GPTBot) but does almost nothing about ad-traffic bots and bad-actor visits. This guide covers the layers you can add yourself and the layers that need a tool.

On this page

    The problem in one paragraph

    GA4's built-in bot filter relies on the IAB/ABC Spiders & Bots List, which covers known good-faith crawlers but not malicious bots, scrapers, or low-quality ad-traffic. Audiences built on top of polluted data feed bad signals back to Google Ads and Meta optimisation algorithms.

    What Google Analytics (GA4) catches automatically

    • IAB-listed crawlers (Googlebot, Bingbot, AhrefsBot, etc.)
    • Known good-faith spiders
    • Obvious user-agent strings declaring themselves as bots

    What slips through

    • Headless browsers that present a normal user-agent
    • Residential-proxy bots that look like consumer traffic
    • Spam-referrer traffic and ghost-spam injected via Measurement Protocol
    • Scraper bots harvesting pricing and content

    Recommended tools

    Ranked by buyer fit for this specific platform, not by commission rate:

    CHEQ Essentials

    Tags GA4 sessions with a bot-or-not classification via dataLayer; you can then build audiences that exclude flagged sessions.

    Cloudflare Bot Management

    Blocks at the edge before GA4 even fires. Best if the bot problem is also a server-load problem.

    Manual: GA4 internal traffic filter + audience exclusions

    Free option. Workable for low-traffic sites; impractical at scale.

    Highest-risk verticals on this platform

    Publishers, e-commerce, lead-gen, SaaS with self-serve sign-up flow. Advertisers in these verticals see invalid-click rates well above the platform average and should treat protection as table-stakes, not an optional layer.

    What to do this week

    1. Pull last 30 days of platform data and identify your top 10 invalid-click flags (high CTR + zero conversion patterns are the easiest tell).
    2. Apply the free fixes first: placement exclusions, content-category exclusions, partner-network toggles where relevant.
    3. If your spend on this platform is above USD 2,000/month and you are in a high-risk vertical, trial one of the tools above for 14 days and measure the ROAS delta.
    4. Document everything — the data you keep this week is what you will need to file refund requests later.

    FAQ

    How do I turn on bot filtering in GA4?

    GA4 has bot filtering enabled by default and there is no toggle to turn it off. The default filter uses the IAB Spiders & Bots List.

    Why does GA4 show traffic from countries I do not target?

    Most likely VPN traffic, scraper bots, or referral spam. Build an audience excluding the unwanted countries and apply it to reports for cleaner data.

    Will filtering bots reduce my reported conversion count?

    It will reduce the noise above the conversion event but conversions themselves are rarely from bots, because most bots do not complete a purchase. So clean data shows the real conversion rate higher, not lower.

    Can I tell Google Ads to exclude bot audiences?

    Yes — build a GA4 audience that excludes the bot-classified sessions, link it to Google Ads, and use it as an audience exclusion on campaigns.

    Is GA4 worse at bot filtering than Universal Analytics was?

    About the same in stock configuration. The bot signal in GA4 is exposed in different reports but the underlying filter is similar.