How to Exclude IP Addresses in GA4 | Steps to Remove Internal Access from Measurement

Essential for accurate access analysis in GA4 is the IP address exclusion setting, which removes access by your own company and stakeholders from measurement. If internal access is included in the data, behavior different from actual users gets mixed in, lowering the accuracy of page view and conversion analysis. In GA4, the mechanism has changed significantly from the previous UA, requiring a two-stage setup: "defining internal traffic" and "enabling the data filter." This article explains those steps following the admin screen operations, and also covers how to verify after setup and what to do when exclusion is not working.

What is IP address exclusion in GA4

IP address exclusion in GA4 means treating access from specific IP addresses as "internal traffic" and excluding it from reports. Internal traffic refers to access by the site operator's side, such as employees of your company or affiliated companies. By excluding this, you narrow the data down to only external, real users, enabling accurate behavior analysis.

What changed between UA and GA4

In the previous Universal Analytics (UA), IP exclusion was completed in a single step with the "Filter" function. In GA4, on the other hand, it has changed to a two-stage method: first you create a definition that marks IP addresses as "internal traffic," then you exclude the marked access with a data filter. This mechanism has the advantage that, even if you mistakenly exclude important traffic, you can verify it in advance in the test state.

Before setup: confirm the IP address you want to exclude

Before starting the setup, first confirm your company's IP address that you want to exclude. GA4's internal traffic definition screen has a "Check IP address" link, from which you can display the IP address of the network you are currently using. If your office has a static IP address, use that value; if you have multiple locations, list out the IP address of each location.

Steps to exclude IP addresses in GA4

IP exclusion proceeds broadly in two stages: "defining internal traffic (creating a rule)" and "enabling the data filter."

STEP 1: Create an internal traffic rule

First, define the target IP address as internal traffic. The steps are as follows.

1. Open "Admin" in GA4 and select "Data Streams" within the property
2. Click the target web stream and select "Configure tag settings" at the bottom of the details screen
3. Click "Show all" to the right of the settings items and open "Define internal traffic"
4. Click "Create" and enter a rule name (e.g., Office IP exclusion)
5. The traffic_type value can be left as "internal"
6. Choose a match type (IP address equals / is in range (CIDR notation), etc.) and enter the IP address you want to exclude
7. If there are multiple, add them with "Add condition," then click "Create" at the end

This makes access from the specified IP addresses get marked as "internal." However, note that at this stage it is not yet excluded from reports.

STEP 2: Enable the data filter

Next, to exclude the marked access from reports, enable the data filter. GA4 has an exclusion filter called "Internal Traffic" prepared in advance, but in its initial state it is set to "Testing" and exclusion is not yet in effect. Because it is provided by default in most web properties, there is no need to create a new one; you just switch this existing filter.

1. Open "Admin" → "Data collection and modification" → "Data filters"
2. Open the "Internal Traffic" filter whose type is "Internal traffic"
3. Confirm the operation is "Exclude" and the parameter value is "internal"
4. First save with the "Filter state" left as "Testing" and verify operation (see the next section)
5. Once you have confirmed it is correctly identified, switch the state to "Active" and save

Only if the internal traffic filter is not in the list, create a new one from "Create Filter" at the top right, with type "Internal traffic" and operation "Exclude."

Test whether the setup is working correctly

To avoid permanently losing data, do not enable it right away; always verify operation in the test state. When the filter is in the "Testing" state, access identified as internal traffic is not excluded from reports but is recorded in a dimension for verification.

1. While accessing the site from the target IP address, open "Reports" → "Realtime" in GA4
2. Click "Add comparison"
3. Select "Test data filter name" for the dimension, set the value to "Internal Traffic," and apply
4. Confirm that your company's stakeholders' access is correctly identified as internal traffic

Compare the data with the filter applied against the data without it; if there is a difference in the figures, the filter is working correctly. Once you have confirmed the identification, return to STEP 2 and switch the filter state to "Active."

It takes time to take effect

It can take from a few hours to, in some cases, around 24 to 36 hours for the data filter setting change to take effect. Because it may not be reflected even if you test right after setting it, we recommend checking after leaving some time.

What to do when exclusion is not working

If your company's access does not decrease even though you set it up, check the following points.

• The data filter is still on "Testing": the most common failure. Defining internal traffic alone does not exclude it; exclusion only takes effect once you set the filter to "Active"
• IP address input error: confirm whether the registered IP address and match type (equals / in range, etc.) are correct
• Mix of IPv4 and IPv6: depending on the environment, exclusion rules in both formats may be needed
• Use of proxy / VPN: confirm whether the actual source IP of the access differs from the set value

For dynamic IP, smartphones, and remote work

In environments where the IP address is not fixed, exclusion by IP address does not work well. Smartphones change IP each time they connect, so they cannot be targeted for IP exclusion. The same applies when working remotely or location-free. In such cases, you can consider introducing a static IP, or connecting to the internal network via VPN to route through a static IP. As a simpler method, using the Google Analytics Opt-out Add-on (a browser extension) to exclude access from that device itself from measurement is also effective.

Points to note when setting up

Finally, here are the points to keep in mind for IP exclusion settings.

• The effect on data from applying an exclusion filter is permanent; once excluded, the data cannot be recovered later. Always test before enabling
• Only up to 10 data filters can be created per property
• In dynamic IP environments, check for IP address changes regularly, such as once a month, and review the settings
• Exclusion is a setting to remove measurement noise; if you only want to temporarily hide it in a report, using a report filter is another option

Summary

GA4's IP address exclusion is completed in two stages: defining internal traffic (creating a rule) and enabling the data filter. If you are used to UA's single-stage setup, it is easy to stumble by forgetting to enable the filter and thinking "it isn't being excluded," so always confirm the identification with a test before switching to "Active." It also helps to keep in mind that it takes time to take effect and that dynamic IP environments require periodic review. Correctly exclude your company's access and proceed with site analysis using reliable data.