GDPR - how to disable munchkin code from Marketo Landing pages | Community
Skip to main content
Jan 3, 2018 10:15 AM UTC
Solved

GDPR - how to disable munchkin code from Marketo Landing pages

We are currently researching different possibilities of opting in and opting out people from being Profiled by Marketo which is one of the GDPR requirements.

I am still in a testing process of placing js script to disable munchkin code from the website, but that made me think about the opting out from tracking on Marketo landing pages.

Any thoughts on that ? How do you approach this limitation ?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
Jan 5, 2018 6:11 AM UTC

This new blog post shows how to defer running Munchkin (Munchkin.init()) until the lead has opted in.

11 replies

Ulf_Deeg
Level 3
Jun 20, 2018 2:14 PM UTC

You are the best. So where would I put the Id and the options?

[Edit] Never mind, I figured it out.

Translate
Chelsea_Stinnet
Level 3
Apr 6, 2018 4:08 PM UTC

@Sanford Whiteman​ can this code for Marketo LPs also be used on corporate websites?

Translate
SanfordWhiteman
Level 10
Apr 6, 2018 5:34 PM UTC

Of course.

Translate
Feb 22, 2018 1:27 PM UTC

Hi Gabby,

There are website compliance software solutions that can present the website visitor with the choice to allow or block cookies by type. For example, they scan your website on a regular basis and present the visitor with an updated list of cookies. They inform the visitor what the cookie does and allows them to both give and withdraw consent.

If this sounds like it may be of interest message me for more details mb@ittrust.eu

Best of luck!

Mihaela B

Translate
SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
Jan 5, 2018 6:11 AM UTC

This new blog post shows how to defer running Munchkin (Munchkin.init()) until the lead has opted in.

Translate
Jan 5, 2018 1:41 PM UTC

Thank you Sanford , very useful blog .

Translate
SanfordWhiteman
Level 10
Jan 4, 2018 4:50 AM UTC

Manually loading Munchkin.init() on a Marketo-hosted LP is tricky, for the same reason that setting init() options (sometimes critical for correct Munchkin operation) is harder in that context.

This blog post explains how to do the latter.

I can write another post on how to delay init() on Marketo LPs, but I first want to double-check your goals. Do you want to prevent the very first pageview from being logged, or has your legal team determined that the first pageview can be logged as long as no further actions are logged? (Logging only the first view may not constitute "tracking" in a legal sense, since you only have one log entry.)

Translate
Community Manager
Jan 3, 2018 4:10 PM UTC
Dan_Stevens_
Level 10
Jan 3, 2018 4:22 PM UTC

@JD, the DNT feature that you refer to is to honor the users' DNT browser settings.  This is a start, but nowhere near the compliance that is needed for GDPR.  What we're hearing - still not 100% certain if this is the case (especially once the recommendations by the ePrivacy Directive are included) - is that you need to disable all cookies (except those that are required to keep your site functioning properly) by default.  This includes Munchkin tracking.  You would then serve up a consent modal to get users to provide their explicit consent to have Munchkin enabled on their browser.  And there lies the rub.  Can you imagine having these modal windows pop up on every site that want to install tracking cookies on your device?  It will be interesting to see how this plays out.

Translate