Does Google Analytics Track IP Addresses?

So, does Google Analytics actually track IP addresses? The short answer is yes, it collects them, but no, you can't see them. This setup can be confusing, but it's a critical part of how Google balances providing useful data with protecting user privacy. This article will explain exactly how Google Analytics uses IP addresses, why they are hidden from your reports, and what this means for your data analysis and compliance efforts.

Graphed

Still Building Reports Manually?

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

Watch the Demo

How and Why Google Analytics Uses IP Addresses

An IP (Internet Protocol) address is a unique identifier assigned to every device connected to the internet. Think of it like a digital mailing address. Google Analytics needs to briefly access this address when a user visits your website for a couple of important reasons, the main one being geolocation.

When someone lands on your site, an Analytics tracking code sends information about their session back to Google's servers. This data packet includes the user's IP address. Google's system then looks up that IP address in its database to determine the user's approximate physical location.

This is how you get valuable geographic reports in your GA account, showing you data broken down by:

• Continent
• Sub-continent
• Country
• Region (State or Province)
• City

This information is incredibly useful for marketers and business owners. It helps you understand where your audience is concentrated, which locales are driving the most valuable traffic, and where you might want to focus your advertising efforts. For example, if you see a surge of high-converting traffic from a new city, that could be a signal to run a targeted ad campaign there.

However, it's essential to understand that this data is aggregated and anonymized. Google Analytics won’t show you a report mapping individual IP addresses to specific user sessions. Instead, it tells you that you had "1,000 sessions from London," not "Session XYZ came from IP address 81.2.69.142." Google uses the IP address to get the location data and then, for all intents and purposes, discards it before it's ever logged or reported.

Beyond geolocation, IPs are also helpful for data filtering, like excluding traffic from your own company's computers to keep your data "clean." You can create a filter that tells Google Analytics to ignore all activities from specific IP addresses (like your office network), ensuring your internal page views don't skew your metrics.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why Can’t You See Full IP Addresses in Your GA Reports?

The primary reason you can't see a visitor's full IP address in Google Analytics is privacy. In many parts of the world, including Europe under the General Data Protection Regulation (GDPR) and California under the California Consumer Privacy Act (CCPA), IP addresses are considered a form of Personally Identifiable Information (PII).

Personally Identifiable Information is any data that can be used to identify a specific individual. This can include names, email addresses, phone numbers, and, in this case, IP addresses. Google's Terms of Service strictly prohibit sending PII to its servers. Storing or making user IP addresses visible would be a direct violation of this policy and could create significant legal risks for both Google and website owners.

To avoid this, Google Analytics has built-in mechanisms to process IP addresses without storing them personally. Here's a simplified look at what happens behind the scenes:

1. A user visits your website.
2. The GA tracking code sends a hit to Google's servers, which includes the user's IP.
3. Google's data collection servers use the IP address immediately to derive geographic location.
4. Before the hit data is logged and processed for reporting, the IP address is made anonymous or outright deleted.
5. The anonymized, aggregated data is then made available in your GA reports.

This process ensures you get the geographic insights you need without ever storing sensitive personal data, keeping you on the right side of privacy regulations.

A Tale of Two Analytics: IP Handling in GA4 vs. Universal Analytics

How Google Analytics handles IP addresses has evolved. The new standard, Google Analytics 4, is much more privacy-centric by default than its predecessor, Universal Analytics (UA).

Universal Analytics (The "Old" Way)

In Universal Analytics, the version of Google Analytics heavily used until 2023, IP addresses were collected by default. However, UA also offered an "IP Anonymization" (or IP masking) feature. When enabled, it would instruct Google's servers to remove the last part - or "octet" - of the user's IP address before it was stored. For example, an IP address like 122.48.65.123 would be modified to 122.48.65.0. This made it impossible to identify a specific device, providing a layer of privacy.

The catch? Website owners had to manually enable this feature. Many were unaware it even existed, leaving them collecting and storing partial-but-still-identifiable information without realizing the privacy implications.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Google Analytics 4 (The "New" Way)

With privacy becoming a central concern for users and regulators alike, Google took a different approach with GA4. In Google Analytics 4, IP addresses are not logged or stored under any circumstances. IP data is only used momentarily to determine broad geographic location (country, city) and is then immediately discarded.

There is no option to turn this on or off, IP anonymization is mandatory and built-in. This is a significant leap forward for privacy. It removes the burden from website owners to configure settings correctly and ensures that GA4 is compliant with major privacy laws like GDPR from the moment it's installed. For EU-based traffic, the initial data collection and IP lookup even happen on EU-based servers before being forwarded for processing, adding another layer of compliance.

Practical Analysis Without IP Addresses

Okay, so you can't see IPs. Does that mean your analysis is limited? Far from it. What you really want from an IP address - understanding your audience's location and behavior - can be achieved much more effectively using GA's other features.

1. Lean on Geographic Reports

The primary use case for IPs in analytics has always been location, and GA4 provides that information cleanly and clearly. Navigate to the Reports > Tech > Tech details section in GA4, and you can change the primary dimension to "Country," "Region," or "City" to see where your users are. You can analyze user engagement, conversion rates, and revenue for each location to identify your most valuable markets.

2. Implement User-ID Tracking

If your goal is to track a specific user's journey across multiple sessions and devices, IP addresses were never a reliable way to do it. A user's IP can change when they switch from Wi-Fi to cellular data or move from their home to a coffee shop.

A far better method is the User-ID feature. When a user logs into an account on your website, you can assign them a unique, anonymous identifier (like user-12345). By passing this ID to Google Analytics, you can stitch together their entire journey — from discovering your brand on their phone to making a purchase on their laptop — without using any PII. This gives you a crystal-clear view of customer behavior and helps you understand how different channels contribute to conversions over time.

Graphed

Still Building Reports Manually?

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

Watch the Demo

3. Leverage Google Signals

Google Signals is a feature that aggregates anonymized data from users who are signed into their Google accounts and have turned on Ads Personalization. Activating Signals can enhance your reports with cross-device capabilities and give you more demographic and interest data. It helps fill in the gaps for understanding who your users are (in an aggregated, anonymous way) without violating privacy.

4. Focus on First-Party Data

Ultimately, the most valuable insights come from your first-party data. This is information your customers voluntarily share with you, such as through a newsletter signup, a contact form, or their purchase history in your CRM (like Salesforce or HubSpot). You can import this data into GA4 to enrich your analysis. For example, you can analyze the behavior of high-value customers identified in your CRM to find patterns you can use to acquire more customers like them.

Final Thoughts

In short, while Google Analytics technically "uses" IP addresses to figure out where your visitors are coming from, it doesn't log, store, or show them to you. This is an intentional and important design choice that protects visitor privacy, and with GA4's default anonymization, it makes compliance with global data laws much simpler for everyone.

Analyzing performance across different platforms like Google Analytics, your ad accounts, and your CRM can be a huge time-sink. Instead of spending hours pulling data and trying to connect the dots manually, we built Graphed to do the work for you. We help you connect all your data sources in one place so you can use natural language to create dashboards and answer questions in seconds. Simply ask, "show me traffic and conversions by country from Google Analytics last month," and get a real-time, shareable dashboard instantly, all without worrying about the underlying complexities of PII or API limits.