This content has been marked as final. Show 6 replies
Hi Molly, progressive profiling should work because it's just basing on whether or not the information is known, and not actually passing sensitive information over.
There are a couple of recent threads on this topic:
Thanks Dory! Good to know that it is in fact an option... the issue I'm seeing must have something to do with the way our web dev vendor has set up our CMS to retrieve the forms we've created in our Marketo instance. In a way, it's good to know that it's not a Marketo issue .
I'm also not seeing progressive profiling work on an embedded 2.0 Form. Using straightforward embed code on WordPress-based site.1 of 1 people found this helpful
Are there some specific nuances that need to be adhered to?
Hi Ron, I'm interested in the same thing. We want to use progressive profiling on our 2.0 Form in our website hosted in WordPress. Have you had any success since this string?
Progressive profiling started working on Forms 2.0 at some point in time (can't remember exactly when.) So that issue seems to be resolved (at least for us.)
Our biggest concern currently with Forms 2.0 is that it doesn't render correctly or at all for some legacy IE browsers (8.0, 9.0) that are still in use by some large, conservative enterprises (our customer base.)
Hi Ron -- we're in the exact same boat! We found that IE9 in compatibility mode is the biggest issue -- and of course, the majority of our corporate clients have outdated versions of IE as their default browsers :) We're in the process of troubleshooting it now with our website developers. When I get some info on a fix, I will let you know!
We were ultimately able to get progressive profiling to work. We realized we had the munchkin, but not the munchkin tracking code, in place. Once we added that additional .js snippet, it worked for us.