Bot filtering
FunnelTrack automatically detects and blocks pixel hits from bots, crawlers, and scrapers — so your destinations only receive real visitor activity.
What it does
Every pageview and event your pixel sends to FunnelTrack is checked against a list of known bot patterns before anything else happens. If the hit comes from a bot, it's silently dropped:
- It's not counted against your monthly event quota
- It's not sent to Meta, Google Ads, TikTok, or any of your other destinations
- It doesn't show up in your event logs or attribution data
The result: your reports, ad-platform conversions, and audience-match data only reflect actual humans visiting your site.
What gets blocked
FunnelTrack recognizes around 3,000 known bot patterns, including:
- Search engine crawlers — Googlebot, Bingbot, DuckDuckBot, Baiduspider
- AI scrapers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider
- SEO tools — AhrefsBot, SemrushBot, MJ12bot, Screaming Frog
- Link previewers — facebookexternalhit, LinkedInBot, Slackbot, Discord, Telegram
- Uptime monitors — UptimeRobot, Pingdom, StatusCake
- Headless browsers — automated tools used by scrapers and click farms
The list updates automatically as new bots appear, so you never need to manage it.
Where to see it
Open Usage Logs in your dashboard. The Event Deliveries stat tile at the top of the page shows a small footer line:
Hover the question-mark icon for a quick reminder of what it covers.
Frequently asked questions
No. Filtered hits are removed before any quota counting happens. You only pay for real visitor traffic.
The list focuses on confirmed bot signatures — user agents that bots openly identify themselves with. Real browsers don't match these patterns. We're conservative about what gets dropped to make sure you never lose a real conversion.
The current filter catches bots that identify themselves honestly. We're building additional layers to catch automation tools that try to impersonate real browsers — those will roll out over the coming weeks. In the meantime, if you ever notice unusual traffic patterns, reach out and we'll help investigate.
The default protection is always on and is a core part of how FunnelTrack keeps your attribution data clean. If you have a specific reason you need a particular bot to come through (for example, your own QA monitoring), let us know and we'll work with you.
Probably not — most analytics platforms either don't filter bots at all (so their pageview count is inflated) or filter them differently. Comparing FunnelTrack's pageview count to Google Analytics or your CMS's stats won't be apples-to-apples. FunnelTrack's count is what your ad platforms actually received.
Why it matters
Bot traffic doesn't buy your product, fill out your forms, or become a customer — but if it reaches your ad platforms, it pollutes everything downstream:
- Inflated conversion counts make your ROAS look worse than it is
- Bot IPs and user agents get added to lookalike audiences, dragging down match quality
- Bid optimization algorithms learn to target whatever the bot signal looked like
- Your event quota burns faster, costing more without any real attribution value
Quietly dropping bot hits at the front door fixes all of that — and you don't have to think about it.
Related: Custom loader · Ad-blocker bypass
Internal trigger reference: detection: "ua_match" (see bot_filtered_log for forensics).