Stop invalid email from synchronizing with SFDC.

[JC100]

Hi there,

Is there a method to prevent the sync of the lead with the invalid email to salesforce?

For example:

• The form submission with an incorrect email will fail.
• Only after the email is confirmed valid (e.g. the thank-you email is delivered) will the lead be synchronized to salesforce.

Our sales are tired of handling leads with invalid emails.

Any advice would be helpful. Thank you!

[Darshil_Shah1]

New people created in Marketo/existing Marketo-only records don't get synced over to the CRM via native sync until you sync them implicitly or explicitly. You must have a setup in your Marketo that's syncing new people getting created in your instance over to the SFDC, you can adjust the campaign's criteria to ensure that a Marketo-only record syncs with the CRM only after it meets your criteria to be considered as a record with valid email address (e.g., the thank-you email is delivered). You can use "SFDC Type" = Empty for filtering Marketo-only records.

[TiffanyD · Accepted solution]

One way to do this is by creating an operational smart list to reference in choice logic whenever a sync to SFDC action is in a flow. 

This would be used in choice logic to effectively not sync the record at the sync action - 

You would need to make sure timing of these steps is in alignment with your email followup/invalid flows so that you don't sync before the invalidation can occur.

This won't work if you are using the native program-level campaign sync.

[JC100]

Thank you Tifanny! When I say "invalid" email, I mean it doesn't exist, but it appears the filter can only identify text that doesn't look like an email (e.g. without @), so we may use the email delivered as a filter. FYI

[FahadRiazRao]

Email Invalid field mentioned above is mechanism inside MKTO. This gets true based upon Hard Bounce captured by MKTO on sending the email to the lead. So it covers everything around validity including @. Hope it helps here.  

[SanfordWhiteman]

---

This gets true based upon Hard Bounce captured by MKTO on sending the email to the lead. So it covers everything around validity including @.

---

This is not true. A domain that cannot receive mail (but doesn’t return an SMTP-level failure) will not Hard Bounce.

[TiffanyD]

You could use both filters if you reference it in a global smart list!  That would cover multiple bases for your team.