SanfordWhiteman

Karina, any action that loads images counts as an Open.

It's not the onSuccess, it's that you have this broken code:You can't declare objects like that -- it's a syntax error.The fieldMap is an array of objects:See Custom Form to Marketo Form Submit

If you have other identifying values that were imported, you can use the API to import and dedupe on another field. Or if the email address is another field, use Change Data Value. However, in the event of a bad import all your columns are probably messed up.

It's Sanford Whiteman actually. You can always target a single Marketo form by checking the ID:MktoForms2.whenReady(function(form){ var formId = form.getId(); if ( formId == 999 ) { /* stuff for only form 999 */ }});

It's Sanford Whiteman actually. ("... 2" is one of my secondary accounts.)As you've discovered, even end-to-end SMTP success from one sending server (i.e. Outlook/Exchange) to the remote mailbox doesn't mean that you won't get an SMTP error from another sending server (Marketo), since servers vary...

With the upfront warnings that...[a] changing an address from an apparent typo should only be done for leads who aren't engaged; and[b] if you "fix up" user-provided input incorrectly, you may end up spamming another person... then this is quite easily automated using FlowBoost:var domainMisspelling...

Completely​ agree, Leanne... this policy shouldn't be enforced without consulting real engagement numbers. Guessing whether leads are legit can be fraught with errors.

That's a way to do it, Raymond. But you can do the same thing from the destination LP itself. (And you don't necessarily need to refresh the page after clearing the cookie, you can delete and reinsert the form. Though it's easier to refresh you should then skip the Visit Web Page for the second page...

It's certainly possible to void the cookie and create a new association based on the URL token. How are you trying to do this?

Has to be supported, otherwise the endpoint doesn't make a whole lot of sense.I'm on a plane right now so can't verify, but try lookupField:email and pass cookie: in the lead record.