Update Consent After Bounce Correction

After reading this cool blog from Amey Holden, my brain went into turbo mode. What happens after the correction?

This is what my amazing colleagues Dalí, Lotte, Nuno, Marco, Robbert, and I started thinking about. The email address that bounced must have received an email to bounce, right? So, it probably has some consent records attached to it. What if we automagically transfer these records to the corrected email address? 🪄 That’s what we have built together, and I have the pleasure of showing you how!

Updating Consent

Our starting point is the “Email Address Bounce Review Required” field on the contact. If this changes to ‘No,’ it means the email address has been updated to the correct one.

We start with a modified “Email Address Bounce Review Required” field on the contact.

We then check if the field value equals ‘No.’

Next, we list all the contact point consent records for the bounced email address (we used an additional field for this).

We then check if there are any contact point consent records listed.

This is the expression we used.

length(outputs('List_All_Contact_Point_Consents_for_the_Contact')?['body/value'])

For each row, we check whether it is a purpose or topic contact point consent record. See the Microsoft documentation on this as well.

Finally, we create new contact point consent records for the new email address.

For creating a topic contact point consent record, it should look like this.

Here is what the entire flow looks like!

Some Nice Adjustments to Consider

This is just a basic setup. You could refine it to make it look and work better ✨. Consider the following:

1. What if the ‘corrected’ email address is already in the system with an existing contact?
2. What if the ‘corrected’ email address already has contact point consent records attached to it?
3. Make the creation of these records optional; give the user the option not to create these records.
4. Should we make it a plug-in instead of a Cloud Flow?

Special Thanks!

I want to give a special thanks to my colleagues who helped me build this cool flow. Big shout out to: Dalí, Lotte, Nuno, Marco and Robbert!

Thanks to Timo for the opportunity to get this group together in a mini-hackathon!

And to Amey, for providing the starting point for this blog post!