Tokenized Sending lets you use data for your messages that is deemed too sensitive to store in Salesforce due to laws, regulations, or security policies. To protect sensitive information across clouds, use tokenized sending with Marketing Cloud Connect for Marketing Cloud Engagement.
For example, sensitive information can include:
- Personally Identifiable Information (PII)
- Protected Health Information (PHI)
- Any other information you prefer to retain on your own servers
The tokenized sending process transmits information from your data systems to Engagement at send time using an API call. Data is never stored in Salesforce. Instead, your Salesforce org stores a single token, resembling a standard email address, per subscriber. Each token can contain a collection of attributes about that subscriber. Sensitive data received from the token exchange is discarded from memory and not retained in Marketing Cloud. However, all tracking and deliverability data is available in Engagement, identified by the subscriber key.
If tokenized sending is provisioned for your account, keep these considerations in mind when using it with Marketing Cloud Connect.
- Recommended for use only with new accounts.
- Works with all Engagement account types using subscriber keys.
- Contact, Lead, and Person Account records in Sales and Service Clouds must use the token as the main email address.
Review all other Engagement considerations and best practices for tokenized sending.
