Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
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...
Query parameters are all after the ?, yes. Like key=value&key2=value2, etc.If the query parameter is not present, you'd just send them to a default choice.
The custom HTML (and CSS) ensures that that the act of showing the Known Lead HTML in turn hides the entire form.
The code that calls MktoForms2 methods must appear after the forms2.js script is loaded.
The CDATA wrapper isn't affecting it -- see my response to your other question.