UTM and analytics view filters
Analytics filters (internal traffic, developer traffic, bot exclusion, source overrides) can quietly change how UTM-tagged visits are reported. This page explains the safe ways to filter without dropping legitimate campaign data, and the filter mistakes that make UTM numbers look wrong.
Filters that touch UTM data
Several common filters interact with campaign data, sometimes unintentionally:
- Internal-traffic filters — exclude your own team, but can drop tagged test clicks
- Bot/spider exclusion — removes known bots, including some that follow tagged links
- Referral exclusion lists — can override an explicit utm_source
- Source/medium overrides — auto-tagging can outrank a manual UTM
Order and scope matter
In platforms that apply data filters before processing, a rewrite or exclusion is permanent for that view — you cannot recover the data later. Test filters in a staging or testing state before enabling them, and keep an unfiltered raw view so you can audit what a filter removed.
A common surprise: a developer-traffic filter set up during launch keeps excluding real visits if its definition is too broad.
Don't let auto-tagging fight your UTMs
When a platform appends its own click identifier and you also add UTMs, the tool may favor one over the other. Decide per channel which wins (commonly: let the ad platform auto-tag, and use UTMs everywhere it cannot), so the same click is not attributed two different ways.
How it appears in analytics and logs
If a filter unexpectedly drops or rewrites UTM traffic, a campaign appears to underperform for reasons unrelated to the campaign. Understanding filter order and scope explains those discrepancies.
Diagnostic use case
Configure analytics filters so internal and bot traffic are excluded while UTM-tagged campaign visits are preserved and attributed correctly.
What WebmasterID can help detect
WebmasterID separates bot and internal traffic from human campaign visits server-side, so UTM-attributed numbers are not silently reshaped by a misconfigured view filter.
Common mistakes
- Leaving a broad developer/internal filter on after launch, excluding real campaign visits.
- Applying a destructive data filter without keeping an unfiltered raw view.
- A referral exclusion overriding an intended utm_source.
- Letting auto-tagging and manual UTMs double-attribute the same click.
Privacy and accuracy notes
Filter on coarse, non-identifying signals (internal traffic ranges defined by you, declared bots). Do not build filters from personal data, and keep UTM values free of anything identifying a visitor.
Frequently asked questions
- Can a filter delete my campaign data permanently?
- In analytics tools that filter at collection or processing time, yes — excluded hits are not stored. Always keep an unfiltered view and test filters before enabling them.
Related pages
- UTM parameters and bot traffic
Tagged URLs get fetched by more than humans: crawlers, link-preview unfurlers, security scanners, and uptime monitors all follow UTM links. Counting them as campaign clicks inflates results. This page explains why bots hit tagged URLs and how to separate automated traffic from human campaign visits.
- UTM validation and QA
Most UTM data problems are preventable with a validation step before links go live. This page describes what to check on every tagged URL — presence of the core parameters, lowercase consistency, proper URL encoding, no double question marks — and a lightweight QA workflow so broken or inconsistent tags never reach production.
- UTM vs click IDs (gclid, fbclid, msclkid)
UTM parameters are manual labels you write; click IDs like gclid, fbclid, and msclkid are opaque identifiers a platform auto-appends. This page explains how they differ, which tools read which, and why setting conflicting manual and auto-tagged values on one URL causes double-counting.
- Bot vs human
Separate bot and internal traffic from human campaign visits.
Sources and verification notes
- Google Analytics Help — About data filtersHow data filters include or exclude traffic, including bots.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.