SanfordWhiteman

Generally, if faced with this situation I would pass _method=delete in the query string as an override. Of course, the server needs to know to translate the call back to DELETE.

I like that hint text, Carlos! It just might do the trick.

The asterisks represent your company's Marketo data (your Munchkin ID and Marketo instance).Your developer will know what to do if s/he is already using the embed code.

A lead only gets his/her own data injected into the page. There's no leakage.

On that page, I don't see any onSuccess handler.I only see the default embed code:

If the user has their mailto: handler set to Outlook, then any mailto: link opens in Outlook (how do you know that your users are using that app?).You can't add attachments from the user's computer via a mailto: link. It would be a pretty obvious security violation when you think about it.

Easy peasy. Add a hidden form to the landing page. Form prefill injects all desired field values into the DOM. Read values out with JS + apply classes, set element styles, etc.

Well, you have an errrant "true;" in your code, so there's probably a syntax error. I hope you're looking at your browser's console/developer tools to see such things.The correct code is demoed here. The onSuccess is called as expected. However since that page doesn't have your GTM code, it fails...

I don't care about the Best Answer (okay, just a little bit) but want to show it can be done straightforwardly. When we use auto-submit forms we make sure the form is prefixed with "Hidden", "Silent", "AutoUpdate", etc. to set it apart. With the Munchkin call, that's also cool, but it means another ...

@John W You don't need !important because .mktoForm span.mktoButtonWrap.mktoSimple button[type="submit"].mktoButtonhas higher specificity than .mktoForm .mktoButtonWrap.mktoSimple .mktoButton@Mel P The CSS I posted is demoed here.If you need advanced CSS customization I think you may have to h...