Google Analytics Adds Include Filters for Hostnames to Simplify Spam Blocking

Google Analytics has introduced Include data filters for hostnames, allowing website owners to define an approved list of domains rather than manually blocking spam sources one by one.

The update appeared in a September 21 entry on Google's "What's New in Google Analytics" page and was reported by Search Engine Journal senior news writer Matt G. Southern on September 22, 2026. The change marks a significant shift in how properties can manage incoming event data and maintain analytics accuracy.

For digital marketers and analytics professionals, this update addresses a long-standing pain point. Managing an ever-growing exclude list of spam hostnames has historically demanded constant manual attention. This new allowlist approach promises to reduce that maintenance burden while strengthening the integrity of analytics data — and for teams who rely on accurate Google Analytics metrics to inform decisions, cleaner incoming data has a direct downstream impact on every report they rely on.

---

How the Include Filter Changes Hostname Filtering

What the Include filter does differently

Until now, hostname filters in Google Analytics operated exclusively as Exclude filters. When Google first introduced hostname filtering on June 11, its release note described the feature as letting customers "filter out (exclude) events based on their hostname." The Include filter reverses that logic entirely.

Google's release note explains the reasoning directly: "Previously, filtering was limited to Exclude filters, which required ongoing manual updates to keep up with new sources of spam. By allowing you to define a list of approved hostnames, this feature simplifies configuration and helps ensure the integrity of your analytics data with minimal maintenance."

With an Include filter in place, a property owner lists their approved production domains once. Any event data arriving from a hostname not on that list is blocked automatically. The practical benefit is clear: instead of chasing new spam domains as they appear, analytics managers maintain a single clean allowlist that does the work for them.

There are two important exceptions to how the filter operates:

• Events sent through the Measurement Protocol will not be affected by the Include filter and will remain unblocked.
• Events that arrive with no hostname at all will be blocked. Google's release note uses gtag.js traffic as an example and states that "a missing hostname typically indicates spam or abnormal traffic."

Why this matters for data quality

Spam traffic distorts session counts, inflates bounce rate figures, and corrupts conversion data — making it harder to draw reliable conclusions from your analytics. Maintaining clean, trustworthy data is foundational to effective measurement, and the Include filter is a meaningful step toward reducing the noise that has historically crept in through spam hostnames. Understanding how this fits within a broader SEO and analytics measurement strategy will help teams get the most from the change.

---

Critical Steps Before Activating the Filter

Understanding the permanent consequences

The stakes around activating an Include filter are high and users should proceed carefully. Google's data filters operate on incoming data only and evaluate events "from the point of creation forward," meaning historical data is not affected. However, once a filter is set to Active the consequences are permanent.

Google's data filters help page states explicitly that matching events blocked by an Active filter "will never be available in Google Analytics or BigQuery." There is no recovery option for data that gets filtered out after activation.

Using Testing mode before going live

To reduce the risk of misconfiguration, Google provides a Testing state for data filters. In Testing mode, matching events are tagged with a "Test data filter name" dimension rather than being dropped outright. This allows administrators to review which events would be affected before committing to full activation. Google also notes that a data filter can take 24 to 36 hours to fully apply after changes are made.

Google's setup page for hostname filters recommends testing a filter before activation, and analytics professionals should treat this guidance as mandatory rather than optional given the irreversible nature of Active filters.

Before activating, work through the following sequence:

1. Navigate to Admin and open the Data filters section to confirm the Include hostname filter is available in your property.
2. Build your approved hostname allowlist and set the filter to Testing mode.
3. Allow a minimum of 48 hours in Testing mode and review the "Test data filter name" dimension to confirm no legitimate traffic is being caught.
4. Document your approved domains clearly within your team so the allowlist remains accurate as your web infrastructure evolves.
5. Activate only once you are confident the allowlist is complete and correct.

There is no rollback option once a filter moves to Active status. The time invested in thorough testing is always worthwhile.

---

What Remains Unclear About the Rollout

Open questions on subdomain and multi-domain handling

Several questions about the new Include filter remain unanswered. Google's release note does not explain how Include matching handles subdomains or properties that receive event data from multiple hostnames. That ambiguity could create complications for larger organisations or those running complex multi-domain setups.

The release note also provides no rollout timeline or confirmation that the Include option is available in every Google Analytics property. Users who want to check availability can navigate to the Data filters section within Admin to see whether the option appears in their property.

A recurring documentation gap

As of September 22, Google's hostname filter setup page and its broader data filters overview still describe the feature as exclude-only. Southern noted in his reporting that a similar documentation lag occurred when he covered Google's AI Assistant channel in May, suggesting the gap between product updates and documentation updates is a recurring pattern for Google. Teams should check the official Google Analytics data filters documentation directly for the most current guidance rather than relying on third-party summaries during active rollout periods.

The broader context for measurement accuracy

The update arrives at a time when data quality and measurement accuracy are under increasing scrutiny across the digital marketing industry. As AI-driven analytics tools become more central to business decisions, the reliability of the underlying data flowing into those systems carries growing weight. Teams exploring more advanced approaches to visualising and interrogating their data — including using Google Analytics alongside heat map tools — will find that the value of those techniques rises significantly when the underlying event data is free from spam contamination.

Three actions to take now

For analytics managers and digital marketing professionals, this update offers three clear opportunities:

1. Review your Data filters section in Admin to confirm whether the Include hostname filter is available in your property.
2. Build your approved hostname allowlist and run it in Testing mode for at least 48 hours before activating.
3. Document your approved domains clearly within your team so the allowlist remains accurate as your web infrastructure changes over time.

A well-maintained allowlist now could save significant cleanup effort as spam sources continue to grow in volume and sophistication.