SanfordWhiteman

I agree about the latency of the Segmentation, Mark.

Everyone's contributing creative and complementary solutions, which is great.If you want the simplest possible path as you're not a JS developer, and one that will cover the most common use/abuse cases, add this at the top of the Thank You page:

Yeah, it doesn't sound like you should be using an IFrame at all. That isn't going to gain you anything and it's just going to make it harder to access the form elements. I'd go back to an embedded form.If you can alter the login page, you can hook the submit process for the login form and copy th...

P.S. If you follow me on the Community I can keep you posted on a solution we have that actually does allow prefill from external pages. But at the same time, some of things in your initial post ("When a user signs in...") make me think you're expecting Mkto forms (regardless of where they're hoste...

So are you confirming the problem is resolved/nonexistent? I had no problem submitting from Chrome and IE11. Can you replicate the problem with that one member of your sales team?

Anthony, there really isn't any such thing as a "Marketo IFrame." I mean, in practice, that may be what we call it, but what it really is is a Marketo Landing Page that holds only the one Marketo form, and then that LP is placed inside an IFrame in a 3rd-party site.By only having one form take up t...

No prob. Here's the recipe I put up a while back: MktoForms2 :: Field Confirmation

You need.mktoForm .mktoRequiredField .mktoAsterix { display: none;}because of CSS selectivity rules.

That error isn't from an http/https conflict. It's what happens when you hit a page using a hostname that isn't in the SSL cert. For example, I could set up www.nelson.net to point to the same IP as www.marketo.com. But if I went to nelson.net, my browser would barf because Marketo's cert doesn't co...

Using UTM params is indeed another good approach. Different from the idea of a meaningful URL prefix, though.