Marketo GDPR Compliance-a summary of key ideas

[Grégoire_Miche2]

Long time since I last compiled a list of ideas. At this point in time, as GDPR is now less than 3 months away and since everybody recognises that this is not just a EU issue, here is a list of existing ideas that we would really need to see implemented in order to make Marketo a tool that really helps marketers to be and remain compliant

Starting with information capture:

• Admins should be able to force users to add an opt-in field to a form. Vote for
• Also, reordering the fields freely even when we use progressive profiling should not require Javascript. Vote for ​ (Thx Margaux Lepine )
• Capturing opt-in information should also be feasible in the event app. Vote ​(Thx Gunjan Batra )
• Capturing cookie value should not require JS: Vote ​
• We also need to make email click detection more reliable than it is, due to link scanners, since we rely on these events to validate double-opt-in. See ​

We also need to securely be able to process the double-optin, and therefore see removed the flaw inherent to the usage of triggers + filters in "person is created" smart campaign. See

Continuing with information storage compliance:

• It should be possible to anonymize data entries so that we can remain compliant when someone does not agree to be in our database and still get accurate reporting. Vote
• Furthermore, since Marketo email system controls strictly the opt-out, synchronizing our optin field and the unsubscribe one should be a no-brainer. Vote ​
• When we update some's email address and this perso is unsubscribed, Marketo should not automatically re-subscribe the person. This is a serious compliance breach. See (Thx Courtney Grimes )

We also need more flexibility and control on how we can arrange forms:

• It should be possible to move fields below the progressive profiling, especially the opt-in field: ​ (Thx Edward Masson )​, and ​
• And it should be possible to add a text area after the submit button with some legal wording:

Last but not least, GDPR drives to generalize preference center.

• The hard point is enforcing user preferences when running campaigns. This is very error prone and the source of potential huge liabilities. Vote ​

Any key point I have missed ? please feel free to comment, I'll add them.

-Greg

[Grégoire_Miche2]

Added this one:

[Joke_Van_EsDUPE]

@Grégoire_Miche2  All your links are gone...  😐

[Suzy_Lee]

Hi Gregoire,

We set up our Preference Center, and my question is when someone "unsubscribes", does it mean that person should no longer receive marketing email, and/or salesperson personal email?

My second question is in the backend, do you have a similar data folder breakdown like the CASL one (screenshot below), any best practice? In GDPR, do we need to capture why this person consent (event, opt-in email, form opt-in, etc)?

[Grégoire_Miche2]

Hi Suzy,

Please open a new thread. You will get more visibility and more/quicker answers

-Greg

[Grégoire_Miche2]

Added this one: , that is needed to secure the opt-in / double opt-in process.

-Greg

[Grégoire_Miche2]

Added:

•  

[Amanda_Thomas6]

This is great! Thanks, Grégoire Michel​!Grégoire Michel

[Grégoire_Miche2]

Added this one:

-Greg

[Grace_Brebner3]

This is fantastic, Grégoire Michel.

Secondary to the required fields in forms, I'd love to see a mechanism for handling subscription preferences for multiple brands in multiple workspaces under a single partition. It'd be great to have the security of the default unsubscribe field functionality without forcing people to opt out of everything.

[Grégoire_Miche2]

Hi Grace,

This what is about. With this idea, you could define a "brand" tag for programs and automatically assign to each tag value a smart list that would exclude people specifically for this brand.

-Greg

[Gerard_Donnell4]

Hi Grégoire Michel​,

This is a simple suggestion and one that may well exist already, but it bugs the hell out of me. 

The ability to choose the position of the Check Box without having to write CSS rules.

I don't understand why there is not a dropdown to pick where you would like the check box positioned (Left of label).

Thanks,

Gerard

[Grégoire_Miche2]

Yes, the trick is in the "checkboxes" field type.

-Greg

[Dan_Stevens_]

Hi Gerard - you can do this today using the following attributes:

[Anonymous]

Hi Dan,

This was super helpful. Thanks for sharing.

I am interested in how you are presenting the next block of text below what you have highlighted ie "Avande is committed etc etc"

Any tips appreciated.

Mitch

[Dan_Stevens_]

Hi Mitchell - that's just a simple rich-text field:

And here it is live on our site: https://www.avanade.com/en/contact

[Gerard_Donnell4]

Hi Dan Stevens​,

Thanks so much for the tip.

When I tried this and made the field required the asterix is floating way up above it.  You don't know the css used to target that asterix?  I have tried a few different combinations and the style doesn't seem to take effect; and as its a form, I don't have the ability to add the style inline.

Thanks,

Gerard

[Dan_Stevens_]

Hey Gerard - since we're only capturing required data, we no longer need to indicate which fields are required.  Therefore, we use this custom CSS on our forms (when they're used on Marketo LPs):

.mktoForm .mktoAsterix {
    display:none!important;
}

[Gerard_Donnell4]

Ahh,

Unfortunately, my form is asking for extra non-required information and the problem I have is that I only need to target the single asterix of the "terms and conditions" field.  I have tried targeting the specific form label but it doesn't work and the div's on the forms don't have ID's.  I guess I'm going to have to get creative and use some javascript.  I should actually rephrase that last line to "Get creative and ask Sanford Whiteman​ for the solution".

[SanfordWhiteman]

Include my FormsPlus::Tag Wrappers script.

Then each of the rows will have a data- attribute like

<div data-wrapper-for="termsAndConditions">

and you can use that in your CSS:

.mktoForm [data-wrapper-for="termsAndConditions"] .mktoAsterisk {
  display: none !important;
}

[Gerard_Donnell4]

Thanks Sanford Whiteman​,

I owe you a pint for this one.