AnsweredAssumed Answered

Google Personally Identifiable Information (PII) Policy vs. GET parameters

Question asked by 063d160b94ea8db5563720372fed528a055eed1b on Oct 31, 2016
Latest reply on Oct 31, 2016 by sanford.whiteman

Hi All;

we're currently using lead fields as GET parameters in URLs of our landing pages to pre-populate forms for known leads. E.g.{{lead.First Name=}}&{{lead.Last Name=}}&{{lead.Email Address=}}

Recently, Google released a note about Personally Identifiable Information (PII). According to that note, if we build a URL that contains lead's personal info using GET parameters, and use that URL in any of Google services (e.g. AdWords, Analytics etc.), that will count as publishing lead's personal data. And "In the interests of protecting end user privacy, Google ads product policies mandate that publishers must not pass any data to Google that Google could use or recognize as personally identifiable information (PII)"; otherwise they will disable our remarketing lists.


Did any of you face the same issue, and do you have any experience in / ideas about resolving it?


We tried using Marketo Lead ID as the only GET parameter, as it's a unique identifier associated with lead's personal data. But that's even less safe: replace one character in the ID and if you're lucky, you get another lead's data in your form.


Is there any proven workaround like encrypting the field values in the URLs?