[SalesForce] Drawbacks of Marketing Cloud field level encryption

I have a client who has sensitive data that they will be connecting to Marketing cloud via Marketing cloud connector. I'm investigating whether field level encryption is the way forward once the data is in the Marketing cloud.

The help resource does hint at some losses in terms of functionality in the email application after field level encryption has been turned on. What I am trying to understand is once field level encryption is turned on for an account is the functionality of using for instance Data filters and application import turned off for all data extensions or only the data extension that have encrypted fields?

How does things like dynamic content and personalization in emails work with encryption turned on? I'm concerned that by turning encryption on some of the nice functionality is lost especially with regards to preview, segmenting domain reports etc.

Any other considerations to take into account before suggesting this solution?

Best Answer

there are quite a few limitations you need to be aware of with field level encryption. Some of the big ones are:

  • Data Filters are not supported
  • You cant use encrypted values in where clauses
  • Standard email domain reporting is not supported as the email addresses in the contact record are stored as @exct.net
  • The default behaviour of where email addresses are retrieved from is changed when FLE is turned on

You shouldnt have any issues with import activities as these still work correctly. Also send previews all still work correctly

Hope that helps

Related Topic