Has anyone successfully created a "floating" form on a Marketo landing page?

[Anonymous]

I'm building a new guided landing page template and am running into an issue with getting the form element to populate when I try testing it. The way the page was designed, we have a box on the right-hand of the page that "floats" with the page as someone scrolls down. I put the Marketo form element in this box so that the form is always visible no matter where someone is on the landing page, but I can't get it to work when I try creating a test page from the template and Marketo Support has offered nothing beyond "there's a bug in your template." The box is visible and moves appropriately as I scroll down the page, but the form never shows up.

Has anyone successfully created a floating box on a landing page that has a Marketo form in it? If so, would you be able to share the code or provide recommendations on how to accomplish this?

Thanks!

[Anonymous]

Courtney Kwiatkowski​ FYI. I moved your post to Products and Support​ since it is more a product related question.

[SanfordWhiteman]

Please post your actual page URL.

There's (almost) no reason we can't get the form to do whatever you want, but we need context.

[Casey_Grimes]

Hi Courtney,

This likely depends on how you've set up the page, but you should be applying {position:sticky} to the CSS of the mktoForm div you're using with a Modernizr (or similar) fallback for older systems. This should be compliant with the way guided landing pages are setup.

As Sanford said, being able to see the actual landing page will go a long way towards a specific solution.

[Anonymous]

Thanks for the responses. Here's the test page where I'm not able to get the form element to populate with the form I selected: http://pages.viewpost.com/00---Other-Testing_Test-landing-page.html.

We had an outside developer create the page that I've been working to set up in Marketo with editable elements, so I'm struggling to accurately pinpoint where the issue is.

[SanfordWhiteman]

At a glance, it looks like your developer tried to finesse the embedded form by using a <DIV> with class="mktoForm" and expecting the Forms 2.0 engine to treat that container as the form.  It doesn't work that way.  The container element needs to actually be a <FORM> with class="mktoForm" and id="mktoForm_123" (where 123 is the form id). The <FORM> can be dynamically injected into the DOM -- it doesn't need to be static HTML if you don't want it to be -- but it does need to exist in the DOM before the Forms 2.0 initialization code runs.