How IP anonymization works
Every request a browser makes carries an IP address, because the server needs somewhere to send the reply. Analytics tools historically kept that address, used it to work out roughly where the visitor was, and stored it with the rest of the visit. IP anonymization removes the most identifying part of the address before anything is written down, so what remains points to a region rather than to a connection.
In Google Analytics 4 this is not an option you switch on. IP addresses are used in transit to derive coarse location and then discarded rather than logged, and the behaviour applies to every property by default. In the older Universal Analytics it was a setting you had to enable deliberately, which is why so many implementation checklists written a few years ago still mention it. If you are reading an old audit that tells you to turn IP anonymization on in GA4, the instruction is out of date.
Why IP anonymization matters
Under European data protection law an IP address is treated as personal data, because it can be linked back to a person with help from an internet provider. Storing full addresses next to a record of everything someone read on your site is therefore processing that needs a lawful basis, a retention period and a way to honour deletion requests. Removing the address removes a large part of that burden.
It also reduces what a breach can expose. Data you never stored cannot leak, and for most marketing purposes the full address was never useful anyway — nobody makes a campaign decision that depends on one household rather than a city.
Common mistakes with IP anonymization
The first is assuming it makes a dataset anonymous. It does not. A truncated address plus a device identifier, a timestamp and a page history can still narrow down to one person, particularly in a small town or a niche business. Regulators look at the whole record, not one field, so this is a data minimisation measure rather than a compliance certificate.
The second is forgetting the other tools. Your web server access logs, a security plugin, a chat widget, a form handler and any ad pixel may each keep their own copy of the full address on their own terms. Anonymisation inside analytics says nothing about them.
The third is being surprised when city-level reporting looks vague. Coarse location is the trade you accepted, and it is a fair one.
What to do about it
Confirm which tools still store full addresses and for how long, including your hosting logs and any plugin that records visitors. Write those retention periods into your privacy policy in plain words so the page matches the code, and shorten anything held longer than you can justify.
Where a tool offers a truncation or masking option, use it, and note the setting in your tracking documentation so the next person does not undo it. If location detail genuinely matters for a campaign, ask the visitor for a city or district in the form rather than trying to infer it from network data. A tidy GA4 setup documents these choices once so they survive the next staff change.
