SanfordWhiteman

Is there a reasonable way to do this aside from the API?The level of access necessary to do this is only going to be surfaced via native UI or API. You could use a Marketo LP and specially-crafted Marketo form for the client side, but the final processing would still be via API (i.e. passing form v...

You can already build such an interface -- in fact I would say this is one of the more reasonable things to use the API for.

Not using JS in an email.

This is actually is kinda possible. Building right now for a client, though with booleans rather than text, the ability to turn add and remote assignable elements. If I finish a lot of other things I can blog about it.

but it is possible without compromising the security of the data being passed.I just tested the Eloqua "solution" and it is by no means secure. And I'm not even talking about the fact that the demo doesn't use SSL. There is zero security on which pages can use the data service. This is exactly wh...

Well, I was just quoting you about the security. I doubt the Eloqua solution actually does respect security in the manner required. You see, the principal reason that embedded forms cannot securely include lead data is that there's no restriction on where (as in which hostnames) they can be embedded...

The only way security is preserved is if the calls to the web service are secured by the Origin: header.

Put your tokens inside the object window.mktoPreFillFields (don't use vals/setValues). The order doesn't matter. Not coincidentally, this is the key to making prefill work with embedded forms.

Well, here ya go, ya crazy kids: http://blog.teknkl.com/dark-mkto-alleys-line-break-token/

Exactly!(I left you a message the other day about this btw. Did you get it? You might have missed your chance for a personal walkthrough, though, now that I've decided to go public with it.)