Guide to the GDPR for Advertisers

If you’re based—or advertise to prospects—in Europe, there’s a pretty decent chance you’re familiar with the General Data Protection Regulation (GDPR). It’s a package of new legislative rules being introduced by the European Union to make it easier
for residents of EU countries to protect their personal data online. The regulation was officially approved on April 27, 2016, and will formally go into effect across the entirety of the EU by May 25, 2018. And it’s being heralded as “the most important change in data privacy regulation in 20 years.”

Basically, if you’re based in the EU or you “offer goods or services to, or monitor the behavior of, EU data subjects,” the GDPR will force you to be more transparent regarding the kinds of personal data you collect and what you do with it. Furthermore, prospects must give their expressed consent for you to harvest and utilize that data.

No tomfoolery. No shenanigans. Only the utmost transparency. As you can imagine, this gives consumers more power over their personal data. It also bolsters their rights to know about breaches, to see exactly what you know about them on demand, and to be “forgotten.” If they don’t want you to have their data, you must respect their authority. Failure to comply will result in lofty fines (4% of global annual revenue).

Businesses the world over have been scrambling to become GDPR compliant before the regulation takes effect on May 25, 2018. Facebook is one of those businesses.

In this guide, you’ll find out…

  • What the GDPR is
  • How Google AdWords will be impacted by the GDPR
  • How Facebook will be impacted by the GDPR
  • How to acquire consent
  • A GDPR Checklist

What you won’t find is legal advice, since this article does not constitute legal advice, nor is this information intended to create or rise to the level of an attorney-client relationship. You should seek professional legal advice where appropriate.

With that in mind, let’s get to it!

Leave a Reply

Your email address will not be published. Required fields are marked *