In short. Define agency IP addresses as internal traffic, validate the filter in Testing, then activate the exclusion to remove matching incoming events.
Definition: A data filter in Google Analytics 4 (GA4) excludes incoming event data from processing. Agency test visits can be identified as internal traffic through IP address rules, validated in Testing, then excluded with an Active filter.
Key facts
- As of October 2026, Google's internal traffic instructions require property-level Editor access for this configuration.
- Google's data filter documentation states that filters affect incoming data prospectively; historical data remains unchanged.
- Google's report filter guide describes filters that hide data within detail reports while preserving the underlying data.
How is agency traffic defined?
Google's internal traffic guide identifies website activity by IP address or range. The configuration starts here:
Admin > Data collection and modification > Data streams
web data stream > Configure tag settings > Show more > Define internal traffic
A rule assigns the event parameter traffic_type, whose default value is internal. The IP condition must match the agency's public IP address; the interface includes “What's my IP address?”. In Admin, under Data collection and modification, Data filters > Create Filter > Internal Traffic creates the filter. Exclude matches the rule's traffic_type value.
How is Testing checked before activation?
Google's testing instructions label matching events with the filter name in Testing. The documented exploration settings are:
Technique: Free form
Rows: Test data filter name, Event name
Values: Event count
Filter: "Test data filter name contains [the name of your data filter]"
Application can take 24 to 36 hours. Active applies permanent changes to incoming data; Inactive stops evaluation.
What changes when the exclusion becomes active?
Google's data filter reference states that excluded events are never processed and remain unavailable in Analytics and BigQuery. Switching state later cannot recover events already excluded. Activating an exclusion also leaves previously collected agency visits in historical data, because data filters apply prospectively.
The same reference distinguishes internal traffic, identified by IP address, from developer traffic, identified through debug mode. That is a separate filter type for development activity.
Can test visits be hidden while their data is retained?
Google's detail report documentation lists Test data filter name as an available filter dimension. A report filter can hide matching test data where that dimension is available and compatible with the report. Selecting Add filter, the dimension, Does not exactly match, and the filter-name value applies an exclusion to that report's chart and table. Removing the report filter restores the report's unfiltered view.
Related terms
- GA4 traffic acquisition
- How do I inspect referrer collection in GA4 DebugView?
- How do I build a session segment for AI traffic in GA4 Explorations?
FAQ
Can I remove earlier agency visits with a new data filter?
Google's data filter documentation states that historical data is unaffected. You can apply a report filter where existing dimension values identify those visits.
Why are test visits still visible during Testing?
Google's internal traffic guide uses Testing to label matches for validation before activation.
Sources
- Google Analytics Help, "Filter out internal traffic", undated
- Google Analytics Help, "Data filters", undated
- Google Analytics Help, "[GA4] Apply filters to detail reports", undated
Check how a page reads to answer engines. Open the GEO score analyzer