How to Filter IP Address in Google Analytics 4

Nothing skews your marketing data faster than your own team's activity. Every time someone on your team visits your website to check a new feature, read a blog post, or test a contact form, it gets recorded as a session, inflating your traffic and throwing off your conversion metrics. This article will walk you through the step-by-step process of filtering out internal IP addresses in Google Analytics 4, ensuring your reports reflect genuine customer behavior.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why Is IP Filtering So Important in GA4?

Before jumping into the "how," it's helpful to understand the "why." Filtering out internal traffic isn't just a vanity exercise to make your numbers look better, it's a fundamental step toward data accuracy. Clean data leads to better decisions.

Here’s what happens when you don't filter out your team, your developers, or your agency partners:

• Inflated Session and User Counts: Your marketing dashboard might show a spike in traffic, but if it's just your team refreshing the pricing page, it's misleading. This creates a false sense of performance and can lead you to misinterpret which campaigns are actually working.
• Skewed Engagement Metrics: Internal users behave differently than real customers. They might spend a lot more (or a lot less) time on certain pages, have a 100% bounce rate while testing a landing page, or complete goals that aren't actual conversions. This can wreck metrics like Average Engagement Time and bounce rate, making it impossible to see how real users are interacting with your site.
• Lowered Conversion Rates: If your team generates 500 sessions a month and never converts into a lead or sale, that's 500 sessions with a 0% conversion rate dragging down your average. Excluding this traffic gives you a truer picture of how effectively your site is converting actual prospects.

In short, without IP filtering, you’re making strategic decisions based on noisy, inaccurate data. Fixing this is one of the first and most impactful things you can do after setting up your GA4 property.

The Old Way vs. The New Way: UA vs. GA4

If you’re coming from Universal Analytics (UA), you might remember that IP filtering was a relatively simple process. You’d go to the Admin panel, find "Filters" under the View column, and add an IP address to exclude. It was quick and easy.

Google Analytics 4 handles this differently. Because GA4 is built around a more flexible "data stream" model instead of siloed "views," the process has changed. It now involves two main stages:

1. Defining Internal Traffic: You need to tell GA4 which IP addresses belong to you.
2. Creating and Activating a Data Filter: You need to tell GA4 to actually exclude the traffic you just defined.

This might seem like a few extra steps, but it provides more control and includes a handy testing mode to ensure you’ve set things up correctly before permanently changing your data. Let's walk through it.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How to Filter Your IP Address in Google Analytics 4: Step-by-Step Guide

Follow these steps carefully to ensure your internal traffic is properly identified and excluded from your reports.

Step 1: Find Your Public IP Address

First, you need to know what IP address to filter. The easiest way to find your public IP address is to simply search on Google for "what is my IP address." Google will display it right at the top of the search results.

Copy this number. If you're working in an office with multiple people on the same network, this single IP address will likely cover everyone. If your team is remote, you’ll need to collect the IP address of each remote employee you want to exclude.

Step 2: Navigate to Your GA4 Data Stream Settings

Now, head into your Google Analytics 4 account.

• In the bottom-left corner, click on Admin (the gear icon).
• Under the Property column, click on Data Streams.
• Click on the specific data stream for your website. (Most businesses will only have one).

Step 3: Define Internal Traffic

This is where you tell GA4 what an "internal" visit looks like.

• On the Data Stream details page, scroll down and click on Configure tag settings.
• On the next screen, under the Settings section, click Show all to expand the options.
• Click on Define internal traffic.

Step 4: Create a New Internal Traffic Rule

Now you can create the rule that identifies your IP address.

• Click the Create button.
• A configuration panel will appear on the right. Fill out the fields:
• Click the Create button in the top right to save your rule.

You can create multiple rules here if you need to filter several different IP addresses (for example, for different offices or key remote employees).

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Step 5: Create the Data Filter to Exclude the Traffic

You’ve defined what internal traffic is, but GA4 isn't excluding it yet. For that, you need to set up a Data Filter. This is the most commonly missed step!

• Go back to the main Admin panel.
• Under the Property column, click on Data Settings > Data Filters.
• You might see an "Internal Traffic" filter here with the state "Testing." GA4 often creates this by default. Click on it to configure it. If you don't see one, click Create Filter.

Step 6: Configure and Activate the Filter

Whether you’re editing the default filter or creating a new one, the configuration screen is the same.

• Choose the Internal Traffic filter type.
• Give your filter a name, like "Exclude All Internal Traffic."
• Set the Filter operation to Exclude.
• Check that the filter is targeting the traffic_type parameter with a value of internal (this matches what you set up in Step 4).

Now, look at the Filter state. By default, it’s set to Testing. This is an important feature. While the filter is in Testing mode, GA4 does not exclude the data from your reports. Instead, it adds a dimension called "Test data filter name" that you can use in explorations and reports. This allows you to verify that the filter is correctly identifying traffic from your IP address without permanently losing any data.

After you've confirmed it's working as expected (usually after 24-48 hours), you must come back here and change the state:

• Click on the three dots (menu) next to the filter in the Data Filters list.
• Select Activate filter from the dropdown.
• A confirmation pop-up will appear warning you that this change is permanent. Click Activate.

That's it! The filter state will now show as "Active," and from this point forward, GA4 will exclude all traffic matching your internal traffic rules.

Advanced Scenarios and Best Practices

While filtering a single IP is the most common use case, here are a few other things to keep in mind.

Filtering a Range of IPs

If your company uses a range of IP addresses, manually adding each one is inefficient. In the internal traffic rule settings (Step 4), you can change the Match type to one of the following:

• IP address begins with: Use this if all your IPs share the first few numbers (e.g., 192.168.1.).
• IP address ends with: Less common, but available if needed.
• IP address contains: Useful for complex patterns.
• IP address is in range (CIDR notation): This is the most powerful option for large IP blocks. Your IT department can provide you with a CIDR range (e.g., 192.168.1.0/24). You can just paste that into the Value field.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What About Dynamic IPs?

Filtering becomes tricky when your team works from home. Most home internet providers assign dynamic IPs, meaning the address changes periodically. Unfortunately, GA4 doesn't have a perfect solution for this. Constantly updating the IP list is not practical.

A partial workaround is to have team members use a company VPN that provides a static IP address. When they are connected to the VPN, all their traffic will come from that single, filterable IP.

Key Reminders

• Filters Are Not Retroactive: Activating an IP filter will only affect data moving forward. It will not clean up your historical report data. This is why it’s so important to set this up as soon as you create your GA4 property.
• Don’t Forget to Activate: It’s worth saying one more time - the most common mistake is creating the filter and leaving it in "Testing" mode forever. Set a reminder to come back after a day or two and activate it.

Final Thoughts

Setting up IP filters in Google Analytics 4 is a critical step for maintaining data integrity. By following the process of defining your internal traffic and activating an exclusion filter, you can trust that your reports accurately reflect the behavior of your prospective and current customers, leading to smarter marketing decisions.

Keeping your data clean is the foundation, but the real challenge is turning that clean data into actionable insights without spending all day in analytics platforms. This is why we built Graphed. Once you have trustworthy data from sources like GA4, you can connect it to our platform and instantly build dashboards and get insights just by asking questions in plain English. Instead of manually navigating GA4, you can simply ask, "What were my top performing landing pages last week?" and get a clear, real-time visualization in seconds, freeing you up to focus on strategy instead of report-building.