SanfordWhiteman

Personally Identifiable Information. To the degree that insecure PreFill results in PII leakage (not to mention leaking business IP) to unauthorized external sites, the same is true of your suggestion.Of course if I can ever pub my blog post on scaleable, secure external PF, this won't matter.

I totally agree and when we built this enhancement (for LP Editor, but same idea) there was never a thought of allowing outside links, since the whole idea is to focus marketers on established channels:

This is tantamount to PreFill on embedded forms, since it has the same PII concerns.

Only JavaScript?Wonder if they're using my special sauce.

Justin's saying you can declare mktoString variables, which means you don't have to touch the templates every time for that. It won't be as smooth as if there were a single place to choose the image URL and the attributes, but it would work, giving control to the page author (as opposed to the temp...

I'll blog about it when I have room to breathe.

I have posted 2 different ways to do this with Marketo forms. It isn't necessary to use a separate forms provider (and they don't actually do what Marketo forms do, anyway).

But as I explained, it *is* already possible even on a Free-Form LP using the tiny bit of code I provided (add it to an HTML element).If you're using Marketo LPs, there is never any restriction on accessing lead token values. Even if you choose to use a totally 3rd-party form on a Marketo LP, that t...

I agree completely with Justin's/Marketo's take here re: embedded forms on 3rd-party sites. (There's a simple and secure workaround that I use, but that's neither here nor there.)But that's not really your question. It wounds like you're using Free-Form LPs and that's why you're saying "the landing...