{marketo instance}.marketo.com origin cookies blocked in Safari

[reteshsingh]

Hello,

We are planning to integrate our AEM hosted website with Adobe launch and Marketo. I see another department's website in our company who have integrated with Marketo some time ago shows a different behavior in Chrome browser versus Safari browser.

Under the cookies section in Chrome it shows two origins:

• example.com (our website)
• {marketo instance}.marketo.com

And it does load up cookies for both the origins. So, I think this works as expected.

In Safari too it show the two origins under the cookies section. But cookies for {marketo instance}.marketo.com is not loaded at all.

On this forum, i read - https://nation.marketo.com/t5/product-documents/cname-cloaking-defense-in-safari-and-its-impact-on-m.... But there is no solution mentioned.

I also read Google Chrome can block third party cookies - https://nation.marketo.com/t5/product-discussions/google-chrome-phasing-out-cookies-by-2022/m-p/7062...

There is no mention of a solution in either links above, once cookies related to {marketo instance}.marketo.com origin get blocked on the browser.

Please share your suggestions - I do not know the significance of cookies related to {marketo instance}.marketo.com origin and wondering how important is it in order to track links, page visits and submit lead data to marketo from a website form.

And what happens if it stops working in Chrome as well in near future. 

Looking out for clarifications/solution. Thanks !

[SanfordWhiteman]

3rd-party cookies set at

*.marketo.com

aren’t used by Munchkin in normal operation.

But make sure you’re not using a *.marketo.com domain to load landing pages or forms. Only use your custom Marketo LP subdomain (pages.example.com et al.).

[reteshsingh]

Thanks,  I have one question to ensure I follow if one cookie origin is expected in the browser or two.

Lets say my website is www.example.com and I use standard Munckin JS Form 2.0 JS API to integrate with Marketo. A standard implementation as described in Marketo Documents.

Then once i submit a form using background submission approach (https://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/) - Do I end up observing one origin under the cookies section on browser with name - https://www.example.com ??

If the answer of the above happens to be "YES", then I will assume observing two origin under cookie section on another department website  could be a bug at our end. 

[SanfordWhiteman · Accepted solution]

---

Lets say my website is www.example.com and I use standard Munckin JS Form 2.0 JS API to integrate with Marketo. A standard implementation as described in Marketo Documents.

For clarity, let’s not mix together different technologies.

The Munchkin JS (analytics library) and the Forms 2.0 JS (forms library) are different.  They can work together, but they don’t have to. A form will post regardless of whether the Munchkin library is, or has ever been, loaded. A form can even associate leads if the Munchkin JS is not currently loaded, as long as Munchkin was loaded in the past!

Loading Munchkin alone will not create any 3rd-party cookies.

Loading a form from app-*.marketo.com will create a couple of 3rd-party cookies, but they’re used only for HTTP load balancing, they’re not part of the forms library itself:

__cf_bm

BIGipServersj01web-nginx-app_https