I'm not sure what Marketo can do from their end, as it is more of a browser issue.
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.
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 ?
Yes, that is the recommended way of loading forms2.min.js -- and that's the way it loads on Marketo LPs.
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?
We noticed this issue too. Both our Marketo Forms and RTP Campaigns don't work in Firefox In-Private Browsing. But everything works for IE In-Private Browsing and Chrome Incognito. Definitely looks funny when my in-page default ads don't show on our website? David Myers or Yanir Calisar any ideas on this?
Thanks for the tip Sanford:
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.
Glad to see I wasn't the first to have this problem. Unfortunately, it gets more complex when you use multiple domains. Anyone using iframes to for solve this? Links for the discussions and landing page examples where people have successfully solved the issue? Much appreciated friends!
An iframe will not help you at all here. Iframes don't fool the browser about where content is coming from, though they may fool users.