Hello all! My team has been having issues with our Marketo forms not rendering properly on browsers (namely Firefox) or when there is an AdBlocker. We use a third party website to host our forms - not Marketo LPs. We reached out to support via chat and they thought it was an SSL issue, but it isn't. The form shows fine on Chrome when the ad blocker isn't on.
Has anyone experienced the same issue? Any words of wisdom to share with a newbie here?
Thank you in advance!
Solved! Go to Solution.
It's not directly an SSL issue, but it certainly can be a marketo.com-being-on-blocklists issue.
Ensure you're using your primary LP domain to load form embeds, not the default domain: see https://nation.marketo.com/community/product_and_support/blog/2019/03/26/make-your-form-embeds-happi....
But to follow the above advice w/your corporate site, which is running on SSL, you will have to add SSL to your Marketo subscription if you haven't already. Otherwise the LP domain is not secure (and therefore the embed using the LP domain will fail).
So there is, indirectly, an SSL concern.
You will need to provide a link to the form
It's not directly an SSL issue, but it certainly can be a marketo.com-being-on-blocklists issue.
Ensure you're using your primary LP domain to load form embeds, not the default domain: see https://nation.marketo.com/community/product_and_support/blog/2019/03/26/make-your-form-embeds-happi....
But to follow the above advice w/your corporate site, which is running on SSL, you will have to add SSL to your Marketo subscription if you haven't already. Otherwise the LP domain is not secure (and therefore the embed using the LP domain will fail).
So there is, indirectly, an SSL concern.
Super helpful, Sanford Whiteman! I'll look into adding SSL to our Marketo.
How did you produce the compatibility test below btw?
That's via CrossBrowserTesting.
We got our SSL and swapped out the form embed code with our secured LP domain. We ended up having issues with the submit button not working. We got this error that our lead capture is being blocked by CORS policy.
The difference is the `request-type` was an `OPTIONS` call, not a post call on the form for some reason.
Has anyone encountered this before?
Ensure that you do not have multiple forms on the page loading from different domains (i.e. one using old embed code, one using your LP domain)., That causes this error.
And btw this is how your form looks in 5 major browsers without tracking protection, i.e. not substantively different -- except for in IE 11 where your image on the right doesn't show because of incompatible CSS.