Again, iframed Marketo landing pages are the only option for progressive profiling without writing additional code on top of the embed code. Also, we need to use iframes to get the best of both words of tracking activity in both Google Analytics and Marketo.
Progressive Profiling absolutely works with embedded forms. This is frequently misunderstood.
If you choose to use IFRAMEs in order to get Landing Page impressions, that's your call, but you are explicitly loading an additional document. If you don't cut all the unused junk out of that page, you can't expect it to magically load any faster just because it's not a "real" page. It is fundamentally impossible for it to load any faster than that same page would in a browser.
>>Progressive Profiling absolutely works with embedded forms.
What's the trick to make it work?
These two web pages uses the same form:
1. iframe Marketo landing page: https://neo4j.com/business-subscription/
progressive profile works
2. embedded: Introducing the Neo4j 7-Day Sandbox - Neo4j Graph Database
progressive profile does not work
Thanks.
Actually, they don't use the same form. /business-subscription uses form ID 1386, while /sandbox uses form ID 1186. These forms have different descriptors.
But more important, I don't see /business-subscription (the one you're saying works) using any Progressive Profiling in practice. This is because you have Known Lead HTML enabled, which overrides your attempt at ProgPro. Observe this sequence:
Hi Sanford,
You are correct that the forms are different. Also, on the prog profiling - I made the common mistake of associating pre-fill with prog profiling.
Could you explain where is the setting for: 'Known Lead HTML enabled' ? Do you mean that having Form Pre-fill Enabled, overrides Prog Profiling?
Btw - thank you for taking the time to look at this.
Aileen
"Known Lead HTML" is short for Settings » If Known Lead, Show Custom HTML.
When you enable KL HTML and someone has previously filled in all the default visible fields on a form, the form is hidden and replaced with your arbitrary block of HTML (which can include anything you want, but by default includes the person's First and Last Name and a Download button to jump to whatever asset you otherwise gate with the form).
Therefore, KL HTML can override ProgPro, and PreFill too, since the notions of "show this form with new empty fields," "show this form with prefilled info from before," and "hide this form if we know this person" are in conflict. One of these needs to "win" on every page view.
No tricks. A ProgPro-enabled form on on page w/Munchkin works. I'll check your links later.
I have the same issue. Did anyone come-up with a solution to this yet?
I should add there's no such thing as "just a form that is iframed". Only HTML documents can appear in an IFRAME, not mere HTML snippets. So when people speak of "iframed forms" they always mean "iframed LPs."
Creating a new barebones template, with no Munchkin or any other unused libraries, is the way to reduce the load time of the LP. But I would also rethink the need for the iframe in the first place.
What issue? What's the specific reason you're not using the embed code?