A

Anonymous

Declined

Form Embed - get 'form pre-fill' to work on non-marketo landing pages

Forum|Forum|11 years ago
April 8, 2014
11 replies
6767 views

The javascript for embedding forms in HTML is great, but the lack of 'pre-fill form' and 'progressive profiling' on non-marketo landing page is SO disappointing.

Marketo

A

Anonymous

As the great and all-knowing Beck would say, "Hell yes".

A

Anonymous

sooo disappointing. let's fix this, ASAP, por favor!

Aubrey_Morgan

Level 3

We're using this for our email preference center, and it's making it REALLY difficult for our users to identify what they're already subscribed to. Please enable pre-fill!

A

Anonymous

Would love to see this fixed!

E

Erin_Miller1

Level 2

Why is this not fixed by now?

Lucho_Soto

Level 5

Any updates on this?

SanfordWhiteman

Level 10

ProgPro actually does work on embedded forms.

Prefill does not, and given the stated security position of Marketo, I don't think this will be officially changed in the near future.

But workarounds do exist. I am bound by NDA, but I know there's one out there that works very well and might be released soon.

A

Anonymous

Hi Sangford,

What's ProgPro? I'm not familiar with it. Interesting comment about a workaround...

Carolyn

Robb_Barrett

Level 10

Can't you just set cookies with the info you'd want pre-filled?

Robb Barrett

SanfordWhiteman

Level 10

Not if there are no such cookies because the lead is known, but has never supplied the data in that browser before.

Robb_Barrett

Level 10

Cross browser compatibility is a reach of a user case, IMHO. Most people tend to prefer a single browser, but in any case it's like saying "What if you're on your phone or on your computer?"

I embed my forms on Marketo LPs and use the following code in my forms embed to pre-pop. If you iFramed in a Marketo LP with the form you should be able to utilize this code to pre-pop still. I suppose you could also pass over the {{lead.Lead ID}} in a URL parameter and, on the form, have a hidden field for Lead ID which would pre-pop. I've never tried it before but it seems doable.

form.vals({"PostalCode":"{{lead.Postal Code}}",

"Phone":"{{lead.Phone Number}}",

"FirstName":"{{lead.First Name}}",

"LastName":"{{lead.Last Name}}",

"Company":"{{company.Company Name}}",

"Email":"{{lead.Email Address}}",

"City":"{{lead.City}}",

"Title":"{{lead.Job Title}}",

"State":"{{lead.State}}",

"Address":"{{lead.Address}}"});

Robb Barrett

SanfordWhiteman

Level 10

The definition of Prefill -- as derived from its current implementation and discussed here -- is that it works whenever a lead is known. If it only meant "cache the values the lead entered in the same browser session" then people wouldn't care about it enough to miss it. They'd already be using cookies to persist data.

I totally disagree that cross-device is an edge case. It's the case and the reason this Idea exists. Whenever a known lead reaches a form, people want it to be filled in.

A

Anonymous

Has this been fixed or is there a way around it?