Marketo Cookie Rejection -> Form Data Not Submitted | Community
Skip to main content
New Participant
November 14, 2022
Solved

Marketo Cookie Rejection -> Form Data Not Submitted

  • November 14, 2022
  • 1 reply
  • 2045 views

Hi Marketo community,

 

I have an issue with a hidden form submission after refusing cookie usage (GDPR).

If the visitor chooses to reject cookies or do not activate it through the setting parameters console, our Marketo form renders fine, but the data is not submitted when we trigger the submit button.

In our case, we have a form validation script which allows (or not) to validate the form upstream if all the fields are correctly filled.

Is there a way to submit the form without Marketo cookies being accepted?

 

I've linked the landing page here: Ouvrir un compte entreprise | DHL Express - France

 

Thanks in advance for your help 🙂

Best answer by SanfordWhiteman

Your server changes the response based on the person’s opt-in cookie, after refreshing.

 

Here you see the response if the person opted in. Line #411 loads the Forms 2.0 library. This line does not exist in the response otherwise.

 

(It’s kind of surprising that your web team is not aware that this is the cause, since it’s their own code that determines whether the Forms 2.0 lib and form embed are included.)

1 reply

SanfordWhiteman
New Participant
November 14, 2022

Marketo form submissions in no way depend on cookie support — Munchkin need not even be loaded alongside the form embed. So the problem is clearly in your code. Please link your page so people can observe and debug the error.

yaitmaatAuthor
New Participant
November 14, 2022

Hi Sanford,

Thanks for your response, I've edited my initial post and added the link to the landing page: Ouvrir un compte entreprise | DHL Express - France

 

 

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
November 14, 2022

Your server changes the response based on the person’s opt-in cookie, after refreshing.

 

Here you see the response if the person opted in. Line #411 loads the Forms 2.0 library. This line does not exist in the response otherwise.

 

(It’s kind of surprising that your web team is not aware that this is the cause, since it’s their own code that determines whether the Forms 2.0 lib and form embed are included.)