How to provide option to opt out of Marketo Tracking cookie for website?

[Anonymous]

Looks like the only answer we received was to have the user opt out completely. We used the Unsubscribe field from Marketo to opt them out for now.

[SanfordWhiteman]

The Unsubscribe field has no bearing on whether cookies are set. If the effort is to comply with cookie regulations, you can't do this using lead fields.

[Justin_Cooperm2 · Accepted solution]

In case anyone is wondering, this functionality IS available in munchkin. However, it is only present in versions 152 and up. Currently our production munchkin loader file (http://munchkin.marketo.net/munchkin.js) points to v151.

To take advantage of the functionality, just switch your munchkin tag to use http://munchkin.marketo.net/munchkin-beta.js instead.

We slowly migrate production forward, so after a bit more time passes, you may see the production file  get incremented up. I'll make sure we update the docs to reference the version requirement.

With this in place, just add a query string parameter of "marketo_opt_out=true" to any page that uses Munchkin. This will add a "opt out" cookie (different than the regular munchkin cookie) for the user and will prevent all calls from happening. To opt a user back in, just add "marketo_opt_out=false" to any page that uses Munchkin.

Cheers,

Justin

[Anonymous]

That is excellent news, we will just wait for the version to be upgraded and revisit this again.

[Anonymous]

Hi Justin,

Our current production munchkin loader file also points to v151.

You said its possible to switch munchkin tag to use instead?

Where would I be able to do that? is it a code which need to be added to the page on the top of the munchkin code ?

Is it also possible to apply this logic to marketo landing pages ?

many thanks

Gabby

[Justin_Cooperm2]

It should work if you reference munchkin-beta.js as the link to the munchkin file in your code snippet instead of munchkin.js. Alternatively, it is possible to hard code the actual version of munchkin into the snippet like: http://munchkin.marketo.net/152/munchkin.js

The downside to that is you wouldn't receive future updates to munchkin since you're not going through the loader file. You'd just want to make sure you switch it back to the loader file once v152 or later is the default production file.

Justin

[Yun_Bai1]

Hi Justin, Sanford Whiteman

This post and your comment is very helpful. We are trying to figure out how to stop Cookie tracking on webpage based on GDPR.

You mentioned "Munchkin Beta", while we haven't enable this features, but we still have munchkin on each webpage.  Does this means, we need to turn on this feature first, then go ahead to add "marketo_opt_out=true" on URLs, such as https://”customerpage”?marketo_opt_out=true? , which will stop cookie tracking? Or we can  just directly add  "marketo_opt_out=true" on URLs without turn on above feature?

Thank you,

Becky

[SanfordWhiteman]

If you point me to one of your URLs I'll tell you whether you're on a compatible version already.

[Yun_Bai1]

Hi Sanford,

Please review one of the LPs: https://promo.acronis.com/GDPR-End-User-Corporate-Webinar_LP.html.

Does cookie tracking only happen on Marketo LPs? I know email links will be embed with munchkin, and probably Mkto forms also have munchkin. Form could be sit on a non-marketo webpage. Does the emails and forms munchkin also trigger cookie tracking? 

Thank you,

Becky

[SanfordWhiteman]

Does cookie tracking only happen on Marketo LPs?

Nope, it happens on any site where you load the Munchkin embed code.

I know email links will be embed with munchkin

Nope, email links (by default) will carry a mkt_tok variable to the target URL, but they do not themselves run or require Munchkin at all.

probably Mkto forms also have munchkin.

Nope, forms use Munchkin if available, but they do not require Munchkin nor load it themselves.

Please review one of the LPs: https://promo.acronis.com/GDPR-End-User-Corporate-Webinar_LP.html.

OK, your version of Munchkin is already compatible with the marketo_opt_out=true query parameter.