Today, I’ve received an email from Google about PII
policy breach by displaying information on one of page which has pass PII.
Google adsense PII is Personally Identifiable
Information about publisher. Usually happens when Google detects that publisher
personal information (such as an email address or username) is being passed as
an URL parameter. I've also read some blog posts from several adsense
publishers who have gotten Policy Breach Notice in the few past weeks. In
particular, please make sure that pages that show ads by Google do not contain
your visitors' usernames, passwords, email addresses, or other
personally-identifiable information (PII) in their URLs.
Policy Breach Notice
If you received an email on PII policy breach violations, you
should identify the problem what exactly it, and then we should solve it. When
you’ve resolved the issue by marking “The problem has been fixed” on the form
linked in the original violation email.
Google offers different types of ads tag and
advertising products, and ad size. But whichever type of tag you use, there are
a few things to keep in mind to avoid Google PII notice. In the interests of
protecting Google client privacy, Google ads product policies mandate that
publishers must not fetch any data to Google that Google could use or recognize
as personally identifiable information (PII).
If your site or blog have static pages then is easiest
solution to not place ads on that page because Ad requests typically send a
page URL to Google. So publisher must ensure there is nothing featured in your
page URLs (like publisher email address, username and password) that shouldn't
be sent in ad requests to Google. But if you have dynamic pages where they are
generated more than 10 pages automatically then you need something better. Specifically,
the Identifying Users Policy states that publishers must not fetch any
information to Google as URL parameters.
The basic thinks to avoid PII Policy Breach Notice:
  1. Make sure the URLs of pages where you have applied
    Google ads code do not contain visitor’s email addresses, usernames, passwords,
    or other PII use UUID as user login detail.
  2. Google products allow us to add macros, If you’re using
    a Google product that allows you to add macros, such as the key-values feature
    of DFP, ensure that you’re not placing any information into these macros that
    Google would consider PII.
  3. If your site includes an HTML conversion form, consider
    using the method=POST implementation instead of the method=GET, POST is the
    preferred 'method' for submitting form details.
  4. Make sure that your site do not use email addresses to
    verification as part of site registration/sign up processes.
  5. Do not use key-value and keyword targeting to target
    specific placements on a page to targeting parameter from both the ad tags and
    the ad server or change the targeting values so that PII is not passed into the
    ad request.


Please enter your comment!
Please enter your name here