Elsa_Man1

I agree simply sending out an updated Privacy Policy is NOT compliant in order to continue emailing to them once GDPR has taken effect (unless they've already opted in). The way we're using the Privacy Policy is right at form submission - so before they can submit their data, they need to agree to the Privacy Policy, which means they understand we will store their data in a secure space and they can request us to delete anytime, but they can optionally agree, in a separate checkbox, that they would like to receive future communications from us. So it's 2 separate thing - we're first making sure they understand our Privacy Policy BEFORE they give us any data, and the second is for general email consent. Greg's Salesforce form example is exactly what I meant - you don't need to gather explicit consent to store the data from a form submission, but it can be held within the privacy policy (which many companies have updated to include GDPR sections) so that when people submit the form they have to agree to the Privacy Policy. Which brings me to my original post's point - that we wouldn't be required to delete or anonymize form submission data just because they didn't consent to future communications. ... View more

Both those areas in the GDPR state that data subjects have the right to request their data be erased, basically to be forgotten. So we need to erase their data upon them asking us to. But it does not say we have to ask for their consent to just store the data. We just have to ask for explicit consent to process their data. ... View more

In response to the original idea's note " As part of the GDPR, we need to get consent from people in order to be able to keep their data. If someone registers to download a white paper but does not opt-in, we are supposed to delete the record." Both myself and our legal team here have comb the GDPR, and no where does it say we have to delete their data just because they didn't opt-in to receiving future communications from us. If they are filling out a form and providing information to do so, then your website's updated privacy policy (that should be front and center near the form) should cover the collection of personal data; the explicit opt-in checkbox will be required to cover your company's ability to use that data in things like marketing. When a consumer voluntarily enters in their information via a form in order to receive some sort of value, they are going to accept that their data will go into a secure environment, as outlined in the Privacy Policy on the website. To collect and use the data are two separate things. That's another reason we've all likely seen a ton of emails lately from companies letting us know about their updated privacy policy I think if you were to have any form of data collection points on your site moving forward, i.e. a whitepaper download, but you prefer to only store data from consumers that have opted in, then I would suggest not having a form in the first place. Just have a direct link to the whitepaper, with a subscription form on the side of that page (or at the end of the whitepaper) that asks them to subscribe to continue receiving more content like this. It would achieve the same thing - you only have access to email those who explicitly want you to; you'd retain metrics on the popularity of the whitepaper through page views, as well as how well that whitepaper does at converting visitors to subscribers. Also from Marketo's perspective, they made the decision awhile ago to stop storing anonymous records and making them accessible in our smart lists, etc, in order to not burden their server's resources. The only area you'd see anonymous data now is in the Company Web Activity report. So I'm not sure how they'd feel about opening a similar function back up - my guess is that if they do this, they may just count these "anonymous" records as part of your database size in your Marketo subscription so the burden of cost is not on them; so another possible hypothetical consideration may be if you'd want to pay to keep these records that you can't do anything with, just for the sake of reporting. Just a few of my guesses on why Marketo hasn't really responded to this idea yet, despite its popularity ... View more

Hi Greg - I tried this for 3 of the fields i have (1 is a date field, 1 is a picklist, and the other is just a regular String field), and set them all to Change Data Value to NULL, but in the Results of the Smart Campaign, it says it was all Skipped because "No new value supplied in campaign". Any ideas what's different? thanks! ... View more

Hi Lexi - I'm having the same issue with my sales rep. Can you share what was the solution/cause that you discovered please? Thanks! Elsa ... View more