SanfordWhiteman

No , I am not using a webhook. Instead, am using Marketo's REST API to Create/Update lead, sending data as a JSON response and mapping to custom fields created. Are you accounting for the 10,000 daily API call limit? If not, aren't you inviting a DoS against whatever you're using as a registration...

Also, what you're doing doesn't sound qualitatively different from simply sending any link which Marketo will customize per-lead (and which another lead cannot read or impersonate). What security do you think you're gaining by generating a unique URL (with no other purpose) that ends up being wrapp...

Hence, I am using this entire URL as a token in the email bodies which have the " " part with it as well. As I said, you can't do this and expect Marketo to attribute the click to the lead. You have to exclude the ''.By "exposing REST APIs" do you mean calling out to your external REST APi via a w...

I'd say it's very developer-friendly, close to a no-brainer for a front end dev. It isn't something for users to do (well, they might get lucky with copy-and-paste but won't understand what's going on). MktoForms2 :: Move Field is a quick demonstration of moving fields around in the form. In the ...

You didn't put the inside the form, so that's why it wasn't finding it. It doesn't actually have to be inside the form, I guess, so change to this:MktoForms2.whenReady(function(form){ document.querySelector('#showEmail').innerHTML = form.getValues().Email;})

The link is inserted into the email body as a token from the lead record database as its different for every new user.Unless there is something truly customized about the underlying URL, there's no reason to use a token just to log a lead's click. Marketo will customize the click tracking URL for ...

Does this LP actually have a form on it? Can you post the URL?

I hate jQuery but since it's already loaded, that's the easiest way to wrap it up.

I'd call it beta, but large Marketo instances are using it.

I've got the GA connection, but my point was that the Munchkin cookie may suffice for input (mostly because there is no alternative at present) if the output (display) side can lookup the lead ID, keying on the cookie.That is, for any report you can pull from GA by cookie you could "join" the report...