The October '20 release note mentions the following:
I'm just wondering if anyone can explain this in greater detail. We have a few Marketo forms embedded on our website (not on a Marketo landing page) and it sounds like this update might help with reporting but I'm not entirely certain I understand it.
Solved! Go to Solution.
Instead of your form embed code set up to load directly from a Marketo subdomain
<script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>
your embed code will be updated to whatever is set up as your primary CNAME in your instance (if your domain is secured with SSL)
<script src="//your.domain.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//your.domain.com", "123-ABC-456", 1);</script>
Note this doesn't update wherever you're using the embed code, it just updates what the UI presents to you. You would still need to review wherever you're using the old embed code and update it to the new one.
It shouldn't have any impact on reporting, but it should help deal with adblockers targeting Marketo resources in some circumstances.
Instead of your form embed code set up to load directly from a Marketo subdomain
<script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>
your embed code will be updated to whatever is set up as your primary CNAME in your instance (if your domain is secured with SSL)
<script src="//your.domain.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//your.domain.com", "123-ABC-456", 1);</script>
Note this doesn't update wherever you're using the embed code, it just updates what the UI presents to you. You would still need to review wherever you're using the old embed code and update it to the new one.
It shouldn't have any impact on reporting, but it should help deal with adblockers targeting Marketo resources in some circumstances.
If you're still monitoring this thread:
We have an external website with a Marketo form: https://www.premeramedicare.com. There's a form in the right rail that has been working fine for a year+. Embed code uses the old <script src=”//app-sj01.marketo.com/js/forms2/
Now our embed code has updated to our CNAME but the vendor who manages the site never updated the forms - but they still work.
They added a new page on that site https://www.premeramedicare.com/ms and it has a similar form in the right rail. But the embed code I provided has the CNAME. When submitting the form you'd get an endless Please Wait and an error message. When they changed the embed code to reference the old <script src=”//app-sj01.marketo.com/js/forms2/ - then that form started to work.
Where's the conflict happening?
Wondering if our instance CNAME wasn't properly set up or if it has something to do with our SSL (which we have through Marketo)
<script src=”//app-sj01.marketo.com/js/forms2/ - then that form started to work.
It’s actually sj06, not sj01. But the reason you had the problem is you have two embed codes on that page. All embed codes must use the same domain.