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 ?
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
Hi Sanford- is there also another step that needs to be taken for the munchkin code on non-marketo landing pages- ie our home website w/ forms on it etc.
You can use the same code (Chelsea above had the same Q), but you don't need it on a non-Marketo page, because there you completely control when you call Munchkin.init().
It's different on Marketo-hosted pages because for Munchkin to function correctly, it needs to be injected into the the page automatically by Marketo. This auto-injection includes running Munchkin.init(), thus you need a fancy/hacky override to bring it back under your control.
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.
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.)
@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.
.png)
Adchoices