Personally I've never had a client request to turn off prefill - but I guess we will have to agree to disagree on this one. To bring us back to the original discussion, Marketo form embed does not natively support prefill, hence the table we produced.
To bring us back to the original discussion, Marketo form embed does not natively support prefill, hence the table we produced.
Of course, your empty box for prefill is totally correct! It's the unchecked boxes for Hide form if known visitor and Use fills out form trigger, filter that are incorrect.
BTW, my critique of your table was milder than you took it to be. It's obviously awesome for people to produce documentation where Marketo has a gap and I thank you for that. As a deeply invested user of embedded forms, despite all their foibles, I saw 2 unchecked boxes (plus boxes for conversion and A/B that seem more grey-area or N/A) and for me the that tipped the balance toward misleading. If your primary reason for building the table was to highlight the lack of prefill, then it isn't misleading in that respect.
There is a free WordPress plug-in that should provide the pre-fill functionality. See WordPress › Marketo Forms and Tracking « WordPress Plugins
Sorry, but that plugin is not for professional use. It leaves your Marketo instance open to a simple Denial of Service (DoS) even without malicious use, let alone if someone aggressively attacks you.
We currently iframe our forms that are input into a landing page to match the styling of our website with CSS.
If we embed the forms, what would be the best method in pulling in the CSS styling? Would we have to host a CSS xml file and input it on each page?
When you embed, you can either:
err...I guess this is attempting to be helpful - so I need some help...
I DO want to prefill forms on my website, so until now I thought Iframe was the way to go - in fact the ONLY way to go?
When I mentioned this to the web agency designing the website, they weren't too convinced...they had questions over where on the page the iframe would sit, and how they would be able to control the size of the iframe/forms if we had different sets of fields required for different forms...
I am doing this NOW, so ideas for the future are great - but this will all be done and finished before that functionality comes along I am sure - so I must make a decision now...