Ep. 54 | What You Need to Know about GDPR’s Data Protection Officer

This is a picture of David Fowler for the Rethink Marketing Podcast where he talks about GDPR's new Data Protection Officer requirement

Learn How to Create Other Killer Content to Drive More Leads

This is Episode 54 of the Rethink Marketing Podcast. I am your host, Nathan Isaacs.

In this week’s episode, Act-On CMO Michelle Huff interviews David Fowler about the upcoming European Union’s GDPR and the new role for many companies of a Data Protection Officer.

GDPR is a massive piece of legislation, and it touches all parts of a company from accounting to marketing to legal and even HR. Fowler, who is Act-On’s head of privacy, compliance, and deliverability, said GDPR marks the biggest change to EU data protection in more than two decades.

It applies to the EU’s 510 million citizens, as well as any business doing business with them, regardless of where they are based.

Enjoy the conversation, and we hope you can get one or two takeaways that you can bring to your business.


  1. David, welcome back to the podcast. Can you remind us your role within Act-On?
  2. We’re here today to talk about the Data Protection Officer, which is a new role required under GDPR. Before we get to it, can you remind us what is the GDPR and why we need to know and prepare for it?
  3. How is Act-On fairing in its preparations?
  4. As we mentioned, GDPR is requires each company have a Data Protection Officer. What is the position? What would be that person’s responsibilities?
  5. Why is it needed?
  6. How does a company know if it needs a DPO?
  7. Are there any requirements for being a DPO?
  8. Is this someone that becomes an employee of a company, or are they a hired outside consultant? Do they work just for you or have a handle of clients?
  9. Where does this person live within the traditional teams of an organization?
  10. How does this role tie in with the existing organization? How will they work with someone like you, the Digital Compliance Officer, and someone like me, a CMO, and then with our engineering team?
  11. How do you think companies and/or marketers can use the DPO positively instead of just being a requirement?
  12. How can companies learn more about the role of the DPO and other GDPR regulations?