---
schema_version: "1"
id: 976fdd875633084fd57b96de8bc356ae11e4b99c5dc98724303f37842ab7ac92
title: Unsupported Tokenized Sending Features
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_unsupported_tokenized_sending_features1.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_unsupported_tokenized_sending_features1.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f6a7262ecb8052eceb16f69dbc02d1eecb8474bbf51dde229cd4258ef5757193
description: Tokenized Sending doesn’t work with certain Marketing Cloud Engagement features. Review this list for additional information.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Unsupported Tokenized Sending Features

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.