COOKIE HELL: Marketo Embed Forms No Longer Working with New Cookie Acceptance

[highspot]

Apparently, I am not the first one to post about being in COOKIE HELL with Marketo. I feel comforted by that. 

That said, this doesn't seem like its been directly addressed after pouring through several forum posts on various cookie and Marketo embed forum post to-date. So I'm hoping someone in this community might be up for the challenge to help solve. 

Here's the situation: Our company spent a TON of time (mostly legal and marketing web dev time) making sure our cookie approach is compliant. We leverage a tool called Cookiebot that is suppose to help make sure our cookie policy is compliant. We made a recent update so that visitors to our website can either Decline, Accept, or Modify their cookies through this tool.

Ever since, our embedded Marketo forms on our site seem to be very hit or miss with regard to passing form submissions into Marketo. Especially on Chrome. Sometimes it happens, sometimes it doesnt.... often times you get it to work incognito. It is also impacting our subdomains. 

We've tried to ask Marketo about it. But they said the "form is firing on the backend but the data isn't passing due to cookies.".... what cookies or how to fix those cookies remains completely ineffable. Calling out the Marketo gurus to help. 

[SanfordWhiteman]

Marketo forms do not require cookies. A browser with all cookies disabled (both 3rd-party and 1st-party) can still submit forms and create/update leads.

Now, you can of course have other code on your site that breaks when there’s no or limited cookie support. If that code is responsible for loading a Marketo form, and is unnecessarily dependent on cookies, it may error out before it gets a chance to run loadForm(). But again the Marketo form embed itself does not require cookies. (It does require JavaScript.) The forms library will make use of the Munchkin cookie if it exists, but otherwise will proceed without it

So your web developers shouldn’t be pointing the finger at Marketo — rather, the core issue is sure to be in their own codebase.

But without having access to a page on which the problem is easily reproducible, it’s impossible to troubleshoot further.