Marketing-Cloud-Consultant Practice Questions

Two considerations that should be made about tokenized sending are:

• Personalization strings still allow PII to be displayed within an email. Tokenized sending does not encrypt or mask PII within an email, it only prevents it from being stored in Marketing Cloud. Therefore, personalization strings should be used with caution and only when necessary.
• Service Level Agreements for email sends are unsupported with the inclusion of outside servers. Tokenized sending relies on an external server to provide PII at send time, which may introduce latency or errors that affect the delivery time and performance of emails.

Journey Builder decision splits do not provide a method to access tokenized data natively, but they can be configured with custom activities or API calls to do so. Tokenized sending does not require field-level data encryption for additional security, as PII is never stored in Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_tokenized_sending.htm &type=5