SanfordWhiteman

I assume this is a Marketo-hosted LP. Otherwise, from your brief description, you probably have a race condition causing the code to only work some of the time.

I didn't use any custom code at all. That's just the standard embed code.To fix the "skip" you'd need to use the Wistia API: by definition, there would be no other way to trigger the form to hide in reaction to an event fired on the video player. I updated the demo accordingly.I don't really know w...

I think you're misunderstanding what's being rendered and where. Your JS is executing in the browser, which does not have access to the server-side tokens. You can't create a client-side HTML fragment with dynamic {{my.}}.What you can do is inject all the possible fields into the page in an a JSON o...

Greg, yes, I've already published this recipe: MktoForms2 :: Force known TLD - DNS API Joanna, this code uses a simple real-time check that someone has entered a currently valid TLD, i.e. joanna@a and joanna@a.11223344 will currently fail. Bear in mind that the list of acceptable TLDs is constantly...

Just now, couldn't edit a post because (a) the font color was white and (b) Save Reply wouldn't work. Could copy the text and delete the post. FF 43/Win.Also the stuff Greg and all reported with needing to refresh.

I think the question is why you were expecting that clicking a tracked email link will always re-associate an already-associated cookie with the latest lead. It's not documented to work that way.If you want the most current lead to be associated with future Visit Web Page/Click Link events, then wh...

I don't think that's the Correct Answer since I just got it to work in under 5 minutes. See CodePen - MktoForms2 :: Wistia At 4.5 seconds on the timeline, I have it overlaying a Marketo form.

The Forms 2.0 API only needs the form ID during initialization (after that, it uses a reference to the element). So via cascading callbacks, you can remove the id attribute and create additional copies of the form on the page. I put up this demo some months ago: MktoForms2 :: One Form, Two Renders...

POST /rest/v1/leads.json{ "action":"createOrUpdate", "lookupField":"id", ...}

Yes, Prinu, I believe you have deciphered it: a user registered and then forwarded the confirmation page to someone else.