What would make it much easier to address hard bounces is to populate a flag on the contact or lead record when the email address on that record hard-bounces. When the email address is modified or cleared, the flag would be cleared.
Ideally there would be a system view on contacts and leads that displays these records, so they can targeted for action to correct the email addresses.
It would also allow for a single segment to be created to be used as a suppression segment to exclude these records from customer journeys until the email address is updated.
We are currently performing the same actions using Power Automate and an export of the hard-bounces to populate a custom flag, but this is very tedious and would be much better experience if it was automatic within the platform.
Comments
Kinda geeky but you can populate created field(s) from each journey run with ‘When an action is performed’ from the Dataverse connector. Select: category “Email Channel Journey Start”. Action “Email bounced” from there you can dig and parse json to populate a contact or lead field created to show say bounce type, category, details (note: use multi-line text field).
Category: Segmentation
Hard bounce flagging is very much needed as this is an important indicator of customer data: a hard bounced contact is almost always a lost contact which can be deactivated or otherwise processed.
Currently it is possible to automatize this process by activating the analytics connector which dumps all the interaction data to an Azure blob storage, and then processing the data from there using Power Automate, but this is not really the way most clients want to do this. (Also, tinkering with csv files from the blob storage requires quite lot of skills.)
Category: Segmentation