Bounce replacement of emails for leads that have multiple email fields

[Prakash_Mohanda]

Hello

We have a framework where a lead has 4 different emails. One primary that is used to communicate with them and 3 other options.

1. Email (used for sending emails)

2. Personal Email

3. Business Email

4. Business Email 2

We are a looking for a good way to make sure that we can do replacement of the primary email if it bounces with one of the other email in the priority order listed above. However once bounced email email needs to be tracked on some kind of bounce list so we dont put it back on for that lead as a primary email. it should cycle through each email only once and if it email bounced then it should go into a list or be flagged somehow that we can check before doing another replacement.

looking for some suggestions on how to flag the emails and build a list or custom table to track these bounced email so we can cross check that list or flag before doing a replace.

[Grace_Brebner3]

I would think a set of logic flows like this would potentially work. Thinking on the fly so tokens probably not completely accurate...

To track bounced email addresses:

• Create a "bounced/invalid email addresses" field.
• Create a smart campaign to add bounced addresses to that field:
  • Smart list = your bounce criteria
  • Flow: If "bounced/invalid email addresses" not contains {{lead.email address}}, then change data value of "bounced/invalid email addresses" to {{lead.bounced/invalid email addresses}}, {{lead.email address}} - {{system.dateTime}}.

This will allow you to track all the history of bounced email addresses.

Then, to update the email address field to a new email address:

• Trigger: data value changes, field = "bounced/invalid email addresses" or;
• if you'd rather do as a batch: data value changed, field "bounced/invalid email addresses", new value is not blank, date of change is X
• then, flow:
  • change data value
    • if email address is  {{lead.personal email address}}, change to {{lead.business email address}}
    • if email address is  {{lead.business email address}}, change to {{lead.business email address2}}
    • if email address is  {{lead.business email address2}}, do nothing
    • default: change to {{lead.personal email address}}

Notes:

• You need to be clear on what type of bounces would qualify for the retiring of an email address.
• you'd need to have clear processes for ensuring marketing suspend/email invalid, etc, are updated if the email address is updated.
• You'd also need to think about how these processes work if those fields are not always filled - probably need to expand those flows to filter those blanks out.

[SanfordWhiteman]

I think some of those steps suggest equality comparisons that aren't really possible, though.

[Grace_Brebner3]

Which part(s) do you think aren't possible? Can you not use lead tokens for the choice qualifications? (I've never actually tried them for this purpose).

[SanfordWhiteman]

Yeah, you can't compare token values to field values.

[Grace_Brebner3]

Good to know (though it's a shame)! Thanks.

[Grégoire_Miche2]

Vote here:

and more globally:

[Dan_Stevens_]

Hi Grace - you cannot use tokens in choice evaluations/qualifications.  You can think of "choices" as mini smart list routines within flow steps.  And tokens are not supported in smart lists of a smart campaign.

[Dan_Stevens_]

I like Sandy's explanation better.  Short and sweet!

[Grace_Brebner3]

Good way to think about it though, in that the limitations of tokens in smart lists apply to the choices in a flow . I had simply taken my broader understanding that they do work in the flow steps and assumed it was true for the choices too.