For security reasons, Northern Trail Outfitters indicates they cannot store PII directly within their Marketing Cloud account. They are considering implementing Tokenized Sending to pull PII from their data warehouse at send time. They indicate they send several large, time-sensitive emails per year.
Which two considerations should be made about Tokenized Sending? (Choose 2 answers)
Tokenized Sending allows PII (such as email addresses) to stay external until send time; however, once pulled in via personalization strings, PII can still be displayed within emails.
Since Tokenized Sending relies on live API calls to an external database during sends, Salesforce Marketing Cloud's normal service-level guarantees (e.g., send speed and reliability) no longer apply because they now depend on third-party system response times.
---
Exact Extracts from Salesforce Documentation:
Source: Salesforce Help -- Tokenized Sending Overview
'Tokenized Sending retrieves sensitive customer data at send time, reducing Marketing Cloud's data storage liability. However, if personalization strings reference retrieved fields, PII can still be displayed in the email.'
Source: Salesforce Help -- Tokenized Sending Limitations
'Marketing Cloud does not guarantee service levels for sends that rely on external Tokenized Sending lookups.'
---
Dexter
12 hours agoIrene
6 days agoNadine
11 days agoFelicitas
16 days ago