Bounce replacement of emails for leads that have multiple email fields

[Grégoire_Miche2]

You would have to use a webhook to run the comparisons and store the resulting email address in the email field.

-Greg

[Grégoire_Miche2]

Hi Parkash,

You would need additional fields to flag which emails have been used/tested and became bounced (so 2 checkbox fields for each email address or better yet, 1 text field in which you would store jason data). Then you can either blindly iterate through your email adresses and complete the checkbox or jason fields. You can also use a webhook to run comparisons, and update the email, but you will always need the additional field to know where you are in the process.

-Greg

[Prakash_Mohanda]

I have thought of flags but the real issue i am having is that .... I need to be able to store a bounced or invalid email in a list somewhere once flagged because these emails get replaced constantly by sales and external sources and every time I cycle through them i need to store them in a list that i can compare to later before i replace something.

For example : If email address is flagged as bounce and i replace the email address with personal email address , i need to keep track of that bad email address i just replaced because that same email might come back again via an external data source into one of these email fields.

Is there a way in Marketo to build a list of emails that is not tied to lead records? as in just a simple list of email addresses that i can compare to before i do replacements? i should be able to add and remove emails as necessary from this list.

Another alternative is if the above list doesn't work is , can i create a custom object that has email 1 , email 2 , email 3 and so on as fields and then populate them in sequence for a lead as and when a bad email is flagged?

[Grégoire_Miche2]

again, I would create a lead field, long text, and each time an address is bounced, add to it a line that says {bounces {“datetime”:”20180925 10:04”,”email address”:”myadrress@domain.com”},{”datetime”:...}}. In other terms, for the leads, a log of bounces in JSON format. Then I would use some web hooks to compare any new email address to this log and return a validation of this new address. I might also use some webhooks to maintizn the JSON itself.

Greg