How to Anonymize IP in Google Analytics

Setting up Google Analytics is a great first step, but ensuring you collect data responsibly is just as important. One of the most common user privacy concerns involves IP addresses, and this guide will show you precisely how to handle IP anonymization in Google Analytics to respect user privacy and comply with regulations. We'll cover what it is, why it matters, and how to implement it correctly.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What is IP Anonymization in Google Analytics?

Every device that connects to the internet has a unique Internet Protocol (IP) address. Think of it like a mailing address for your computer or phone. When a user visits your website, your Google Analytics (GA) tracking code records this IP address to get a general idea of the user's geographic location.

However, many privacy regulations, like Europe's GDPR, consider IP addresses to be Personal Identifiable Information (PII) because they can potentially be used to identify an individual. This is where IP anonymization comes in.

IP anonymization (or IP masking) is a feature in Google Analytics that tells Google to obscure part of the visitor's IP address before any storage or processing happens. Specifically, it removes the last octet of the user's IPV4 address (the last three digits) and the last 80 bits of an IPv6 address, setting them to zeros.

For example, a user's IP of 123.45.67.89 would be changed to 123.45.67.0.

This simple change means the full, potentially identifiable IP address is never written to Google's servers. You can still see general location data (like the city or region), but you can't pinpoint the user's exact location, making the data more anonymous and privacy-friendly.

Why Is IP Anonymization So Important?

Implementing IP anonymization isn't just a technical tweak, it's a critical part of modern data responsibility. Here are the main reasons why you should enable it.

Graphed

Still Building Reports Manually?

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

Watch the Demo

1. Compliance with Privacy Regulations

This is the most significant reason. Regulations like the General Data Protection Regulation (GDPR) in the European Union and the California Consumer Privacy Act (CCPA) have strict rules about collecting user data. Since full IP addresses are widely considered personal data, collecting and storing them without consent or a legitimate reason can put you at risk of non-compliance and hefty fines.

Anonymizing IPs is a straightforward technical measure you can take to move towards better compliance. It demonstrates that you are taking proactive steps to protect your users' privacy and process less personal data, which is a core principle of GDPR.

2. Building User Trust

Today's internet users are more aware of their digital privacy than ever before. When they see cookie consent banners and privacy policy links, they are making a decision about whether or not to trust your brand with their data. By anonymizing IPs, you are signaling to your audience that you respect their privacy. This builds credibility and fosters a more positive relationship with your potential customers. People are more willing to engage with businesses they feel are transparent and responsible.

3. Data Quality & Essential Reporting

A common concern is whether IP anonymization affects the accuracy of your analytics data. The good news is that the impact is minimal for nearly all marketers.

Geographic reporting is the only area affected. Because the last part of the IP address is removed, location data becomes slightly less precise. You can still report accurately on users by country, region, and city. You just lose the ability to drill down into a more granular, sub-city level, which most marketing analyses don't require anyway.

In short, you retain all the most important geographical insights required for strategic marketing decisions while significantly improving your privacy posture. A small trade-off for a big win in compliance and trust.

Graphed

Still Building Reports Manually?

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

Watch the Demo

IP Anonymization in Google Analytics 4

If you're using the latest version of Google Analytics, GA4, we have some fantastic news for you.

IP anonymization is automatic and enabled by default in Google Analytics 4. You do not need to take any action to turn it on.

This was a major, privacy-focused change from the previous version of Google Analytics (Universal Analytics). In GA4, Google does not log or store individual IP addresses under any circumstances. When Google Analytics collects data in the EU, the IP addresses are used to derive coarse location data (like city and country) and then are immediately discarded before the data is ever logged to servers in the EU. This ensures user data stays protected inside regional boundaries.

Unlike its predecessor, there is no setting, code snippet, or toggle to turn this feature on or off. If you are running GA4, you are already using anonymized IP data collection. It's built-in, and it’s always on.

How to Anonymize IPs in Universal Analytics (Legacy)

While Google Universal Analytics (UA) officially stopped processing new data in July 2023, many websites still have the old tracking code installed or rely on historical UA data. If you're managing an older setup or auditing a site, it’s critical to know how IP anonymization was implemented in UA, as it was a manual process.

The most common and recommended way to add this setting was through Google Tag Manager (GTM).

Anonymizing IPs with Google Tag Manager

If your Universal Analytics tag was managed via GTM, adding a single field was all it took. Here’s how you would check for it or add it:

1. Log into your Google Tag Manager account and navigate to the container for your site.
2. Click on Variables in the left-hand menu.
3. Look for your "Google Analytics Settings" variable type. If you have one, click it. If you don't, you'll need to find your main Universal Analytics tag under the Tags section and edit it directly.
4. In the Variable Configuration, click on More Settings to expand the options.
5. Go to Fields to Set.
6. Click + Add Field.
7. Click Save to update your variable.
8. Finally, click Submit in the top-right corner of GTM to publish your changes.

This one change in GTM would automatically apply IP anonymization to every Universal Analytics tag that used this settings variable, making it the most efficient way to ensure site-wide anonymization.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Anonymizing IPs Directly in Code (Hardcoded Tracking Snippets)

If your website had the GA tracking code hardcoded directly into the HTML, you'd need to add a line of code. Here were the two most common snippets.

For gtag.js library:

You would look for your Global Site Tag (gtag.js) script and add the anonymize_ip parameter to the config line:

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-YOUR-ID"></script>
<script>
  window.dataLayer = window.dataLayer || [],
  function gtag(){dataLayer.push(arguments),}
  gtag('js', new Date()),

  gtag('config', 'UA-YOUR-ID', { 'anonymize_ip': true }),
</script>

For analytics.js library:

For the older analytics.js library, you had to add a 'set' command before the 'send' command like this:

<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r,i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date(),a=s.createElement(o),
m=s.getElementsByTagName(o)[0],a.async=1,a.src=g,m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga'),

ga('create', 'UA-YOUR-ID', 'auto'),
ga('set', 'anonymizeIp', true),
ga('send', 'pageview'),
</script>

How to Verify IP Anonymization is Working

Whether you're confirming GA4's default setting or checking an old UA setup, you can verify that IPs are being anonymized using your web browser's developer tools.

1. Open your website in Google Chrome.
2. Right-click anywhere on the page and select Inspect to open Developer Tools.
3. Click on the Network tab.
4. In the "Filter" box at the top, type collect to filter for requests being sent to Google Analytics.
5. Now, refresh your webpage. You should see one or more items appear in the network requests list.
6. Click on one of the requests starting with collect. Look at the Payload or Headers section for the list of parameters being sent to Google.
7. Scan through the list for a parameter named aip.

If you see aip=1 in the payload, IP anonymization is active and working correctly. If the aip parameter is missing or set to 0, it is not enabled.

For GA4 users, this check confirms what Google has stated: that the aip=1 parameter is added automatically to all events sent from your website, requiring no additional setup from you.

Final Thoughts

In summary, implementing IP anonymization is a simple but powerful way to make your data collection more responsible and align with global privacy standards. For GA4 users, this privacy-enhancing feature is enabled by default, while Universal Analytics required a small manual update via code or Google Tag Manager.

Once you’ve aligned your analytics with modern privacy standards, the next challenge is turning all that data into actionable insights without the typical drag of manual reporting. We built Graphed to solve exactly this problem. By securely connecting your data sources like Google Analytics, you can use simple natural language to ask questions, build real-time dashboards, and get answers in seconds, not hours - freeing you up to focus on growing your business strategy.