Tokenized Sending doesn’t work with certain Marketing Cloud Engagement features. Review this list for additional information.
- MobilePush, GroupConnect, or Marketing Cloud Connect
- MobileConnect QueueMO SMS API
- SMS conversations, SMS double opt-ins, and SMS messages that use Next Keyword functionality
- Other data privacy features, such as field-level data encryption or data obfuscation
- Journey Builder activities when not storing decision criteria in a clear state or in the Engagement app.
- Segmenting, filtering, or querying when not storing criteria in a clear state or in the Engagement app.
- Execution of Service Level Agreements (SLAs) specifically for sending due to the inclusion of outside servers within the process
- New token creation from a clear email address or mobile number. For every use case, create a token.
- The Resolve Token API doesn’t support passing null attribute values in the response. Therefore, you must omit the null subscriber attribute values from your response.