How PII works in analytics
Definitions vary between laws, but for measurement work the practical test is simple: could this value, alone or joined with something else you hold, point at one named human? Names, email addresses, phone numbers, postal addresses, government identity numbers and account numbers all qualify. So do combinations that look harmless individually.
What matters day to day is that Google’s terms prohibit sending it to Analytics or Google Ads, and Meta’s terms say the same about its own tools. This is not a setting you can switch off. It is a condition of using the product, and the platforms scan for it.
Why PII matters
Because the damage is wholesale rather than retail. A single hit carrying an email address in the page path does not spoil one row; it puts the property in breach, and the remedies available to Google include deleting data or suspending access. There is no way to surgically remove the offending values from data already collected, so a leak discovered late can cost you the historical reporting you were relying on.
There is a legal layer on top. Personal data sent to a platform under terms that forbid it is processing you cannot properly document, and it will not appear in your privacy notice because nobody intended it. And a practical layer underneath: a report full of email addresses in the page report cannot be shared with a client, an agency or a junior analyst without spreading the problem.
Where PII goes wrong
Almost always by accident, and almost always through the URL. A form that submits by GET puts every field into the query string, so the email address lands in the page location of the next page view. Booking systems, password reset flows and account areas put references, tokens and sometimes addresses straight into the path. Chat widgets and survey tools add their own parameters.
The other regular offender is a user ID set to the customer’s email address, on the reasonable-sounding logic that it is unique and stable. It should be an internal identifier that means nothing outside your own database. Worth separating from this: enhanced conversions deliberately send customer data through a sanctioned, hashed channel, which is a different mechanism from pasting an address into an event parameter.
How to act on it
Search your page path and page location reports for an at sign and for long strings of digits, then look at your search terms and event parameters for the same. If you find nothing, check again after every new form or booking tool goes live.
Fix the source first: forms should submit by POST, and confirmation pages should carry a reference that only your systems can resolve. Then add a safety net in your tag manager that strips known parameters and rewrites the page path before anything is sent — redaction after collection is not available to you, so it has to happen before the hit leaves the browser. If you are unsure what your tags are transmitting, a tracking audit is the quickest way to find out.
