Firefox Private Browser Hiding ALL Marketo Embed Forms

[Anonymous]

Anyone else get this problem?

When I use Firefox Private Browsing to visit my website, all of my Marketo embedded forms disappear. It only happens through the new Firefox Private Browsing feature.

[SanfordWhiteman]

I'm not sure what Marketo can do from their end, as it is more of a browser issue.

Exactly.

Most people are unlikely to use private browsing, incognito and whatever the IE equivalent (if any) there is.

IE has InPrivate Browsing, actually has for a long time. 

I agree, most people are unlikely to browse privately by default, and if they do, they have a good reason.

[Grégoire_Miche2]

Hi Sanford,

What if Marketo was providing the forms.min.js library with a URL in the same domain (the customer landing page CNAME) for instance ? Would that work ?

-Greg

[SanfordWhiteman]

Yes, that is the recommended way of loading forms2.min.js -- ​and that's the way it loads on Marketo LPs.

[Grégoire_Miche2]

How can I know the URL in our domain we should use to get it for embedded forms? Or should I juts load the file to our web site?

-Greg

[SanfordWhiteman]

It's always available on your LP domains.

[Grégoire_Miche2]

Cool, Thx.

For the reader: http://[Landing page.sub.domain]/js/forms2/js/forms2.min.js

-Greg

[Grégoire_Miche2]

and vote here:

[SanfordWhiteman]

Sure, new FF has built-in Tracking Protection. This significantly affects both forms and Munchkin.

You can (a) disable TP or (b) try loading all your forms from a CNAME at your domain as opposed to from *.marketo.com.  Search "CNAME" for a bunch of discussions on this.

[Anonymous]

The issue is not with me seeing the forms; my worries are with my potential customers that won't be able to see the forms.

Thanks for advising with that alternate solution, however, I don't believe that changing the 15+ forms that I have on my website is the solution. Marketo should do something about this. When I visit websites that use Hubspot embed forms with Tracking Protection enabled, they show up fine, and they are loading the forms from another domain as well, so the issue is with Marketo only.

[SanfordWhiteman]

Huh?  It's the public tracking protection list that specifically has Marketo domains on it; what would you expect Marketo to possibly do about it?  The fact that TP blocks detected Munchkin hits, for example, is totally sensible.  Marketo is running a tracking service.  You can try to obfuscate this by using your CNAME.  Ultimately, however, if someone is trying not to be tracked, you shouldn't subvert their wishes: that's like trying to sneak JavaScript in even if someone is running NoScript. 

I don't know what you mean by "changing" your forms, in any case.  I'm talking about loading them from your CNAME. You don't have to change anything on the form itself, just the way you load them.

[Geoff_Krajeski1]

I'm talking about loading them from your CNAME. You don't have to change anything on the form itself, just the way you load them.

Exactly, and the best way to do this would be to go to the Admin section > Integration > Landing Pages and create a new Domain Alias that points to your site.

Example:

Type                      Original URL                                   Redirect URL

Domain Alias          http://e.myMarketoDomain.com       http://www.myDomain.com

[Geoff_Krajeski1]

Then in your CMS or website where you are calling the forms, use this aliased domain instead of the Marketo one.

In this way, Firefox will not 'see' it as calling from a different domain when in private browsing mode.     

[SanfordWhiteman]

In this way, Firefox will not 'see' it as calling from a different domain when in private browsing mode.     

I don't think it's about cross-domain scripts in general: that would mean that, for example, it would block jQuery loaded from CDNs.  Rather, it's that Marketo is known to provide tracking services (Munchkin) and this is on some of the big public lists of such domains.

It's perhaps unfair that forms get caught in the crossfire, since they are (mostly) opt-in as far as tracking, but that's what happens sometimes.