How is "Follow Email" field used by Dynamics?

(0) Share

Report

Posted on by Community Member

Hi all,

I was wondering how is "Follow Email" used by Dynamics in terms of GDPR. The description of the field in my instance is "Follow Email (GDPR Consent) - Information about whether to allow following email activity like opens, attachment views and link clicks for emails sent to the contact", but some people is using it as " I consent to X using my name and email address to reply to the submission of this form".
What's the right use and what impact it has in Dynamics?

Thanks.

Categories:

I have the same question (0)

All responses (2)

Answers (0)

Sort by

cloflyMao 25,210 on at

Like (0)

Report
Copy link

Link copied!

Hi Partner,

1. When set this option to Do not allow, no email results will be stored for this contact, it's associated with email interaction.

2. If contact consent his/her name and email address:

There is an existed field called Email(it's logical name is donotemail, you can find it in form editor) with two Allow/DoNotAllow options in CONTACT PREFERENCES section;

for name, you could add a same two option custom field as Email field,

then add these fields to your subscription center page to let your contacts manage their preferences.

From operations above you filter these consent level contacts into a segment based on these field,

and you could let them join in next customer journey.

Here is a detailed consent level list for reference. while GDPR features in Dynamics 365 for Marketing is also described in the article.

Regards,

Clofly

Was this reply helpful? Yes No
Suggested answer

Christian Abeln Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello,

We have a number of channel specific preference fields on the contact and as well the GDPR consent field.

The "Follow Email" field on a contact is a place where for a contact the channel behavior can be stored. The GDPR consent field is a place where a value from different levels of channel independent consent can be stored for each contact. Those fields can be added to the marketing forms such that the desired channel behavior and general consent is known to the marketer.

The information in both those fields shall help the marketer to craft the marketing activities in a way that they follow the given consent of the contact. There is a bit of automatic built in but the main responsibility lies on the marketer to implement the marketing activities to honor consent.

For the "Follow Email" choice we do limit the insights views to not include respective interactions from contacts in the display. But for the marketing automation it is expected that the marketer add respective filter in segments in order to ignore contacts that shall "not be followed" based on email interactions.

The approach follows a is similar pattern like the use of the GDPR consent - it is the responsibility of the marketer to set the minimum required consent on the customer journey such that contacts with lower consent will not progress in the journey pipeline as long as the minimum required consent is not given by the contact. This allows to run reconsenting journeys with lower minimum consent and use less involved messaging and at the same time run rich marketing journey that make use of profiling and automated decision making.

Was this reply helpful? Yes No