Which two implications should a Solution Architect consider if Marketing Cloud Connect is to be used for cloud integration?

A financial services company wants to implement Service Cloud and Marketing Cloud. A number of profile attributes required for personalization in Marketing Cloud were identified as personally identifiable information (PII) and are too sensitive to be stored in Salesforce.

Tokenized Sending was presented as a way to address these concerns.

Which two implications should a Solution Architect consider if Marketing Cloud Connect is to be used for cloud integration? Choose 2 answers
A . The synchronized data extensions will include the token and all PII attributes
B . All emails will need to be sent through Marketing Cloud or Marketing Cloud Connect to avoid disruptions
C . The standard email address field for contacts and leads needs to be populated with a token
D . The token with all supporting attributes will need to be stored in Service Cloud

View Answer

Answer: A,C

Explanation:

Tokenized Sending is a feature in Marketing Cloud that allows sending messages with data that is too sensitive to store in Salesforce due to laws, regulations, or security policies. Tokenized Sending uses an API call to exchange data from an external system with Marketing Cloud at send time, without storing the data in Salesforce. Marketing Cloud Connect is a feature that enables integration between Marketing Cloud and other Salesforce clouds such as Service Cloud.

When using Tokenized Sending with Marketing Cloud Connect, the following implications should be considered:

✑ The synchronized data extensions will include the token and all PII attributes. Synchronized data extensions are tables in Marketing Cloud that store data from other Salesforce clouds using data synchronization in Marketing Cloud Connect. When using Tokenized Sending, the synchronized data extensions will include the token as well as all personally identifiable information (PII) attributes such as name, email, phone, etc. The token will serve as the subscriber key and contact key in Marketing Cloud, while the PII attributes will be used for personalization and segmentation.

✑ The standard email address field for contacts and leads needs to be populated with a token. When using Tokenized Sending, the standard email address field for contacts and leads in other Salesforce clouds needs to be populated with a token instead of an actual email address. The token resembles a standard email address but contains encrypted information about the subscriber. The token is used to exchange data with the external system at send time and send messages to the actual email address.

Option B is incorrect because not all emails need to be sent through Marketing Cloud or Marketing Cloud Connect to avoid disruptions when using Tokenized Sending. However, it is recommended to do so to ensure consistent tracking and deliverability data across clouds. Option D is incorrect because the token with all supporting attributes does not need to be stored in Service Cloud when using Tokenized Sending. The token and the attributes are stored in the external system and only exchanged with Marketing Cloud at send time.

References:

✑ https://help.salesforce.com/s/articleView?id=sf.mc_overview_tokenized_sending1. htm&type=5

✑ https://help.salesforce.com/s/articleView?id=sf.mc_co_tokenized_sending.htm&typ e=0