SanfordWhiteman

Figured it out after more work. It's actually quite easy to trigger (details to follow) and is due to a glaring bug in some 3rd-party JS. Not a race condition or accidental CORS thing. I'll put the explanation up on the blog and link to it here.

@Raul-Ok did you see my response? I’m also curious about the exact need here. Assuming these forms were on Marketing Activities LPs, what could have been done with {{my.tokens}} that now requires a visible form field and label? That’s quite a leap. Are you sure you really need a visible field, not ...

The error is most likely caused by Google Captcha. And I think you have in fact 3 forms on that page. Two of them - the search boxes - point to https://conscia.com/se/ while the Marketo form point to your LP domain www2.conscia.com. I'd investigate in that direction.It’s really only Marketo forms th...

@Christine_LeBla you should read this post: https://nation.marketo.com/t5/product-blogs/every-marketo-field-has-a-friendly-name-a-token-name-a-form/ba-p/358397

Hi, has anyone had any issues that prevent the custom HTML presenting for some returning visitors. It is working for me but not for our website developer.Not an “issue” per se but the person needs to have First Name, Last Name, and Email Address filled for KV HTML to work. Beyond that, we’d have to...

The REST API has robust support for forms. If you want to get your hands dirty it would be a fun way to learn that crazy API. Alternately, you could add the field using JS at runtime (yes, even if it’s a visible field, but it’s super easy if it’s a hidden field). P.S. To be clear for lurkers, it’s n...

Hmm. Your schema really isn’t optimal for such a campaign. Not a fan of anything that needs to extrapolate anniversaries from a Date/DateTime, as Marketo (outside of Velocity, that is) doesn’t have the ability to roll CO fields forward in time. I would probably use a webhook-compatible service and a...