Use landing page subdomain for embedded form library call, instead of Marketo domain | Community
Skip to main content
Grégoire_Miche2
Level 10
April 29, 2016
New

Use landing page subdomain for embedded form library call, instead of Marketo domain

  • April 29, 2016
  • 4 replies
  • 2145 views

When embedding a form, the code provided by Marketo has a flaw that makes it non working on Firefox in private mode. Eg:

<script src="//app-e.marketo.com/js/forms2/js/forms2.min.js"></script>

<form id="mktoForm_XXXX"></form>

<script>MktoForms2.loadForm("//app-e.marketo.com", "999-AAA-999", XXXX);</script>

The first script calls the form2.min.js library in the Marketo domain ("//app-e.marketo.com"), which is blocked by FF in private mode.

It should call the library in landing page subdomain instead, under the form of

<script src="//landing.page.subdomain/js/forms2/js/forms2.min.js"></script>

So that the embedded form also works on FF in private mode.

-Greg

4 replies

SanfordWhiteman
Level 10
April 29, 2016

Pretty sure the PMs said this was going to be changed, but good to have the Idea!

Grégoire_Miche2
Level 10
July 27, 2017

Would have been useful to avoid a lot of trouble with embedded forms during the "domain name renewal crisis".

-Greg

February 6, 2020
No text available