Google Analytics has quietly flipped a core data-quality control. Instead of only excluding spam hostnames one by one, properties can now define an allowlist of approved hostnames and keep event data only from those domains.
What Changed
According to a Sept. 21 entry on Google’s What’s new in Google Analytics page, the platform now supports Include data filters for hostnames. That means you can list the domains you want to keep, rather than adding every bad hostname to an Exclude filter.
Google’s release note frames the shift as an end to manual upkeep. Exclude lists only worked as long as someone noticed and blocked each new spam source. An allowlist puts production domains in once and stops the whack-a-mole.
As Google puts it:
Previously, filtering was limited to Exclude filters, which required ongoing manual updates to keep up with new sources of spam.
How the Filter Behaves
There are two important exceptions. Include filters will not apply to events sent via Measurement Protocol, so server-side data remains unblocked. But events with no hostname at all—such as some gtag.js traffic—will be blocked because a missing hostname usually signals spam or abnormal traffic.
Data filters are also forward-looking only. Google evaluates them from the point of creation onward, so historical data stays untouched. Once a filter is Active, though, matching events are permanently excluded from both Google Analytics and BigQuery.
That permanence makes testing essential. Switch the filter to Testing first; Google will tag matching events with a “Test data filter name” dimension instead of dropping them. Allow 24 to 36 hours for the filter to apply before you activate it.
What to Do Before You Enable This
- Audit every legitimate hostname, including subdomains, payment portals, and checkout domains.
- Create the filter in Testing state and watch the test dimension for false positives.
- Map any Measurement Protocol events separately, since Include filters won’t block them.
- Document the allowlist and review it whenever you launch a new domain or microsite.
Why This Matters for Growth Teams
Clean analytics data is the foundation for performance marketing decisions. Spam hostnames inflate sessions, skew conversion rates, and pollute audiences used in Google Ads and Meta Ads. An allowlist is a lower-maintenance way to protect that data—but it is not a firewall for every scenario.
Google’s release note does not yet explain how Include matching handles subdomains or properties that receive data from several hostnames. If you run a multi-brand property or rely heavily on Measurement Protocol, test carefully before moving to Active.
What to Watch Next
There are no rollout details yet, so the Include option may not be in every property. Check Admin > Data filters to see if it’s available. Google’s help documentation still describes hostname filters as exclude-only as of Sept. 22, so expect the product and docs to catch up gradually.
The short version: if you’ve been maintaining an Exclude filter, an Include filter can remove that recurring chore. Just don’t skip the testing phase—Active filters are irreversible.
Source: Search Engine Journal
