SanfordWhiteman_2-1703058940885.png

The 3 ‘Email Suspended’ fields cascade across existing Marketo duplicates — somewhat like ‘Unsubscribed’ yet different

SanfordWhiteman
Level 10 - Community Moderator
Level 10 - Community Moderator

You don’t want it with Email Suspended. It doesn’t mess around: if a recipient’s mailserver gave a super harsh “We don’t like you” bounce message, Marketo will block all email to that lead for 24 hours.

 

What’s not formally documented is that Email Suspended, and the related Email Suspended At and Email Suspended Cause, are also set for all other leads that exist at the time of the bounce with the same Email Address.

 

This makes sense, of course. We’re trying to give a decidedly unmellow mailserver time to calm down and accept our email again. So hitting it with another send that qualifies the duplicate lead will just make it madder!

 

You’ll first see Email Suspended Cause set for the specific lead who bounced:

SanfordWhiteman_2-1703058940885.png

 

Then a moment later you’ll see the duplicate(s) updated:

SanfordWhiteman_3-1703058955402.png

 

Lead #1132890 is being updated in the second screenshot, but notice how the Reason refers to the bounced lead, #1132889.

 

That automatic sync across duplicates is somewhat like the Durable Unsubscribe feature, but different in 2 notable ways:

  1. Durable Unsubscribe not only cascades Unsubscribed=false across duplicates automatically, it also remembers if Unsubscribed was false at the moment the last lead with a given Email Address was deleted and restores the false value if a new lead is created in the future. Email Suspended fields do not persist after deletion.
  2. Durable Unsubscribe applies to people created either before or after Unsubscribed was set to false. In contrast, the Email Suspended cascade only applies to duplicates that existed at the moment of the hard bounce, not leads created later.
194
0