GDPR Constituent Preference Examples

This article includes some examples so you can see how existing constituent communication preferences have been transferred into the new Preference Centre

Constituent does allow contact

In this example the constituent allows 'default' contact and has no exceptions, these are the changes made

  • the new 'General' purpose and all other purposes have been added in an allowed state as 'default' contact was allowed
  • Preferred channel has been set based on default contact details
Old Communications Preferences New Preference Centre

 

Constituent does not allow contact

In this example the constituent does not allow 'default' contact, these are the changes made

  • the new 'General' purpose has been added in a blocked state as 'default' contact was not allowed
  • all other purposes have been added in a blocked state as 'default' contact was not allowed
  • Preferred channel is set to do not contact
Old Communications Preferences  New Preference Centre

 

Constituent allowed default contact but has some Communications Exceptions 

In this example the constituent allowed 'default' contact and had some exceptions, these are the changes made

  • the new 'General' purpose has been added in an allowed state as 'default' contact was allowed
  • Preferred channel has been set based on default contact details
  • Exceptions have been mapped to purposes as follows
    • the exception that was explicitly blocked - i.e. events - is now a blocked purpose
    • the exceptions that were explicitly allowed - i.e. membership & campaigns - are now allowed purposes
    • the exceptions that were not previously applied - i.e. administration and other - are allowed purposes

 

 Old Communications Preferences New Preference Centre

 

Constituent blocked default contact but has a Communications Exception 

In this example the constituent blocked 'default' contact but had one exceptions, these are the changes made

  • the new 'General' purpose has been added in a blocked state as 'default' contact was not allowed
  • Exceptions have been mapped to purposes as follows
    • the exception that was explicitly allowed - i.e. campaigns - is now an allowed purpose
    • all exceptions that were not previously applied - i.e. administration and other - are blocked purposes
  • The preferred channel is based on preferred channel for the allowed exception

 

Old Communications Preferences  New Preference Centre
 
Have more questions? Submit a request

Comments

Powered by Zendesk