How to Not Count IP Address in Google Analytics

Nothing skews your website analytics faster than your own team's activity. Every time you, a developer, or a content editor visits your site to check on changes, test a new feature, or simply read the latest blog post, Google Analytics logs it as a regular session. This article will walk you through exactly how to exclude your IP address in Google Analytics (for both GA4 and Universal Analytics) so you can get a cleaner, more accurate picture of your actual customer traffic.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why Bother Excluding Internal IP Addresses?

Filtering out your own traffic might seem like a small detail, but it has a surprisingly big impact on your data quality. Inaccurate data leads to poor decisions. When your internal sessions are mixed in with real customer data, it can quietly sabotage your marketing insights.

Here are just a few common scenarios where internal traffic can cause problems:

• Inflated Session and User Counts: If your team works from an office, you could be adding dozens of sessions to your daily count, making it look like your traffic is higher than it really is.
• Warped Engagement Metrics: Your team likely behaves differently than a typical user. They might visit a specific page multiple times for quality assurance or spend a long time on a page a customer would only skim. This can artificially inflate metrics like Engaged sessions and Average engagement time while skewing user flow data.
• Messed Up Conversion Tracking: The last thing you want is for your developers to trigger a dozen “test” conversions while checking a new checkout process, throwing off your conversion rate and making it harder to evaluate campaign performance.

By taking a few minutes to set up an IP filter, you ensure that the data you’re basing your marketing strategy on reflects genuine customer behavior, not your team’s internal activity.

Graphed

Still Building Reports Manually?

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

Watch the Demo

First Things First: Find Your Public IP Address

Before you can exclude your traffic, you need to know your IP address. Think of an IP (Internet Protocol) address as the unique street address for your computer or office network on the internet.

The easiest way to find it is to simply Google it.

1. Open a new tab in your browser.
2. Search for "what is my IP address".
3. Google will display your public IP address right at the top of the search results. It will be a series of numbers, like 72.14.255.104.

Copy this number somewhere handy - you’ll need it in the next steps.

A quick note on static vs. dynamic IPs: Many home internet connections use a dynamic IP, meaning it can change occasionally. Most business and office networks, on the other hand, have a static IP that stays the same. If your team is remote and using dynamic IPs, the basic filter we're setting up might not be a perfect long-term solution. Don't worry, we'll cover workarounds for that later in the article.

How to Exclude an IP Address in Google Analytics 4

Excluding traffic in GA4 is a two-part process. First, you need to define what counts as internal traffic. Second, you need to activate the filter to tell GA4 to start excluding it from your reports.

Part 1: Defining Your Internal Traffic

Follow these steps to let GA4 know which IP addresses belong to your team.

1. Navigate to the Admin Panel: Log in to your Google Analytics account. Click on the Admin gear icon in the bottom-left corner.
2. Go to Data Streams: Under the Property column, click on Data Streams. Select the data stream for your website (there's usually only one).
3. Open Tag Settings: On the Data Stream details page, scroll down and click on Configure tag settings.
4. Define Internal Traffic: On the next screen, click Show all if you don't see the option, and then click on Define internal traffic.
5. Create a New Rule: Click the Create button. Now you'll set up your filter rule:
6. Save Your Rule: Click Create in the top-right corner to save your internal traffic definition.

You’ve now told GA4 to recognize your IP address as "internal." But by default, GA4 still includes this traffic in your reports. The next step is to activate a filter that officially excludes it.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Part 2: Activating the Internal Traffic Filter

Now that your "internal" traffic is defined, you can flip the switch to start filtering it out.

1. Navigate to Data Filters: In the left-hand Admin navigation menu, go back one step. Under the Property column, click on Data Settings > Data Filters.
2. Review Your Filter: You'll see a pre-made filter called "Internal Traffic." GA4 automatically creates this for you. It's in Testing mode by default.
3. Activate Your Filter: Click the three vertical dots (kebab menu) on the right side of the "Internal Traffic" filter and select Activate filter from the dropdown menu.
4. Confirm Activation: A pop-up will ask if you’re sure. Click Activate.

The filter's state will change from Testing to Active. That's it! From this point forward, Google Analytics will stop processing traffic from that IP address in your standard reports. Keep in mind that filters do not apply retroactively, they only affect data collected after they are activated.

A Quick Word on Filter States in GA4

Filters in GA4 have three states, and it's helpful to understand what they do:

• Testing: The filter is running, but it's not yet applied to your main reports. You can check its effect by using the "Test data filter name" dimension in the Realtime report to see if traffic from your IP is being correctly identified.
• Active: The filter is live and permanently excluding the defined traffic from your reports. This change is irreversible.
• Inactive: The filter is turned off and is not excluding any data.

Managing Multiple & Dynamic IP Addresses

In the real world, you often need to block more than just a single IP address.

Excluding an Entire Range of IP Addresses

If your entire company works from one office, your IT department can often provide you with an IP range that covers all devices on the network. In GA4’s traffic definition rule, instead of "IP address equals", you can select "IP address is in range (CIDR notation)".

CIDR notation looks a bit technical, like 70.125.0.0/16. This simple format represents a whole block of IP addresses. If you have the range, you can use an online CIDR calculator to get the correct notation, or simply ask your network admin for it.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Dealing with Dynamic IPs (Remote & Home Teams)

The standard IP filter works perfectly for static IPs, but when your team works from home, their IP addresses often change. Constantly updating the filter list is not a practical solution. Here are two better alternatives:

1. The Official Google Analytics Opt-out Add-on: This is a browser extension provided by Google. Once installed, it prevents any data from your browser from being sent to Google Analytics for any site you visit. Have your team members install this on their work browsers. It's a simple, set-and-forget solution.
2. VPN with a Static IP: For a more robust solution, your company could use a business VPN service that assigns a static IP to all employees. This gives your entire distributed team a single, consistent IP address that you can easily block in GA4 using the standard method.

How to Exclude an IP in Universal Analytics

Though Google is sunsetting Universal Analytics (UA), many people still refer to their old data or manage properties that haven't fully migrated. Thankfully, adding a filter in UA is much more straightforward.

1. Navigate to Admin & Filters: Log in to your UA account and go to the Admin panel. Under the "View" column, click on Filters.
2. Add a New Filter: Click the Add Filter button.
3. Configure Your Filter Settings:
4. Save: The filter will be active immediately.

Final Thoughts

Getting accurate data from your website is the foundation of a smart marketing strategy. Taking a few moments to properly exclude your team's traffic from Google Analytics is an easy but essential step toward data cleanliness, ensuring the insights you rely on reflect genuine user behavior. Whether in GA4 or Universal Analytics, setting up an IP filter means your metrics will be sharper and your decisions more confident.

While properly filtering your IP is a great starting point, the real power comes from unifying all your data streams — not just what's in Google Analytics. At Graphed, we’ve made it simple to connect all your tools like Google Analytics, Facebook Ads, Shopify, and Salesforce in one click. Instead of spending hours in GA4's complicated reports trying to connect dots, you can simply ask questions to your data in natural language and instantly get live dashboards and answers.