SanfordWhiteman

Not at all, but I think we need to be precise about the goal. I opened my own idea about multiple branding domains, in fact.

Sounds like you want to anticipate the, shall we say, "asset to be consumed" and add it as a field within the form itself without supplying it in the URL, rather reading it out of the LP-specific form descriptor. You could accomplish this via this crazy but functional method.Another method, perhaps...

You're mixing up branding domains and landing page domains.The branding domain is go.example.com, click.example.com, etc. -- the click tracker. Has nothing to do with cookies, in fact the branding domain sets no cookies.What you're talking about is "multi-domain Munchkin," which is a different goal...

... well, not so much that only 1 of them will have capability, but more like all clickable links will be rewritten to match only 1 domain (unless you use mktoNoTrack).

I agree with Dan. Even if you make the Submit button double as a (re)subscribe trigger, you still need to label it ("By clicking this...") and they might miss it. So you'd be better off explicitly giving them a checkbox in addition to the Submit.

Yes, ask them why you can't use it as a token, because we use it all the time in our links.I don't understand where you'd need it in a Smart List -- are you matching on a list of SFDC IDs or something?

First of all, using REST/SOAP API calls in response to individual user activities is best left unconsidered, because it creates a DoS vulnerability. I know I say this all the time, but that's because it's a major issue. Any hacker can send 10,000 calls (that's a very, very small number) to a page t...

You can already use the SFDC ID as a lead token.For the data value changed, are you trying to capture the result of lead merge or something?

It's not the ga('create').You're calling ga('send') with four additional unnamed parameters ("positional parameters"): ga('send', 'event', 'marketo form', 'success', ga_label);ga_label is not defined anywhere on your page.I don't know what you want to be sending there, but the script is gonna ba...

Anything that is passed to the page can be, in theory, passed to the back end and in turn populated on the lead.However, I must caution -- as I do frequently here -- against using API calls in response to individual user actions. This setup means your website has an explicit DoS vulnerability. It's...