Hi,
we are experiencing issues with one form that sometimes and to some users returns "Submission failed, please try again” error. I checked this blog and could not find two forms on the page.
The website with the form is here: https://conscia.com/se/event/hur-bygger-vi-framtidens-datacenter-2/
The issue appears randomly to only some users (different browsers, different OS) and there is no pattern that we could identify. We have multiple other Marketo forms across the website, but the issue is present only on this form.
We opened the ticket with support, but they have not come back to us yet. In case someone has any hints on what could be the cause of this error, we would be very thankful to know.
Thank you,
Matjaž
Solved! Go to Solution.
Because I want you to get your forms back in working order sooner than later, let me cut to the direct cause.
The 3rd-party Digital Pi tracking JS has a configuration area where you set up mappings between UTM params and form fields.
You currently have empty strings for three of these:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
utm_content: "",
utm_term: "",
utm_adgroup: ""
}
That won’t work. You need to either self-map those 3:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
utm_content: "utm_content",
utm_term: "utm_term",
utm_adgroup: "utm_adgroup"
}
Or leave them out entirely:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
}
I guess you can’t call it a bug it if it’s documented, but not sure either way!
P.S. All your forms using the Digital Pi JS are potentially affected, not just this one. But other forms may have more fields and that insulates them for an interesting technical reason I’ll get into in the eventual post.
Because I want you to get your forms back in working order sooner than later, let me cut to the direct cause.
The 3rd-party Digital Pi tracking JS has a configuration area where you set up mappings between UTM params and form fields.
You currently have empty strings for three of these:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
utm_content: "",
utm_term: "",
utm_adgroup: ""
}
That won’t work. You need to either self-map those 3:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
utm_content: "utm_content",
utm_term: "utm_term",
utm_adgroup: "utm_adgroup"
}
Or leave them out entirely:
{
utm_medium: "utm_medium",
utm_source: "utm_source",
utm_campaign: "utm_campaign",
}
I guess you can’t call it a bug it if it’s documented, but not sure either way!
P.S. All your forms using the Digital Pi JS are potentially affected, not just this one. But other forms may have more fields and that insulates them for an interesting technical reason I’ll get into in the eventual post.
Thanks Sanford!
The error is most likely caused by Google Captcha. And I think you have in fact 3 forms on that page. Two of them - the search boxes - point to https://conscia.com/se/ while the Marketo form point to your LP domain www2.conscia.com. I'd investigate in that direction.
The error is most likely caused by Google Captcha. And I think you have in fact 3 forms on that page. Two of them - the search boxes - point to https://conscia.com/se/ while the Marketo form point to your LP domain www2.conscia.com. I'd investigate in that direction.
It’s really only Marketo forms that cause that CORS conflict, though.
Unfortunately, I haven’t been able to repro the error despite testing a lot of error scenarios, network/timing conditions, etc. and auditing the code.
Seemingly “random” behavior is usually a race condition under the hood, but I can’t see dependencies like that yet.
Thanks!