Google Analytics Adds Hostname Include Filters

Google Analytics has officially expanded its filtering capabilities by introducing hostname include filters. This update, detailed in a September 21 post on the “What’s new in Google Analytics” page, allows property owners to specify exactly which domains should be retained for event data. Previously, hostname-based filtering was restricted exclusively to exclusion rules. When this filter type was initially launched on June 11, the release notes specified that it enabled customers to “filter out (exclude) events based on their hostname.” The new inclusion model shifts the workflow from blocking unwanted sources to actively permitting approved ones.

Simplifying Data Integrity

The primary advantage of this update is the reduction in manual maintenance. Google frames the shift away from exclude lists as a way to protect data integrity with less effort. The release note states:

“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.”

This approach creates an allowlist rather than a blocklist. Once configured, users do not need to constantly monitor for new spam domains or manually add them to an exclusion rule. Instead, they define their legitimate production domains once, and all other traffic is effectively ignored by the filter logic.

Handling Protocol Exceptions and Missing Hostnames

There are specific technical nuances regarding how these filters interact with different data streams. According to the release note, Include filters “will not be applied to events sent from the Measurement Protocol, ensuring this data remains unblocked.” This ensures that server-side tracking or other protocol-specific data continues to flow regardless of the hostname restrictions.

Conversely, events that lack a hostname entirely are blocked by default. The documentation cites gtag.js traffic as a common example where a missing hostname typically indicates spam or abnormal behavior. This default block provides an additional layer of security against malformed requests.

Testing Before Activation

It is crucial to understand that data filters operate only on incoming data moving forward from the point of creation. Older historical data remains unaffected. Furthermore, once a filter is switched to Active, the action is permanent. Matching events are never processed and “will never be available in Google Analytics or BigQuery.”

Because the change is irreversible, Google strongly advises testing filters before activation. During the Testing phase, matching events are tagged with a “Test data filter name” dimension instead of being dropped, allowing analysts to verify the filter’s impact without losing data. Users should also account for a processing delay, as Google states that a data filter can take 24 to 36 hours to fully apply.

Availability and Future Rollout

While the feature offers significant benefits for managing high-volume spam, the rollout status remains unclear. The release note does not provide specific deployment timelines, leaving it uncertain if the Include option is available in every property yet. Users can currently check the Data filters section within Admin to see if the option is visible in their interface.

As of September 22, Google’s setup pages for hostname filters and the general data filters overview still describe the feature as exclude-only. This lag between the release note and the official documentation mirrors previous updates, such as when the AI Assistant channel definitions did not immediately reflect changes made in May. Until the documentation is updated, users must rely on the Admin panel to determine availability.