---
schema_version: "1"
id: aa2c99afb30dbc56923e4ce6740988889dde322f8d47acdd338a3b61541ab005
title: Token Formats
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_token_formats.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_token_formats.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 21e2c412f0b340998c70bea94c952f275d6fe39a22a9c8a5ecd04b3b54db449c
description: Use email address-based tokens or phone number-based tokens.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Token Formats

Use email address-based tokens or phone number-based tokens.

## Email Addresses

Use syntactically valid, case-sensitive email addresses for email address tokens to pass email validation when importing data or sending email messages. These tokens do not contain the actual email address, but appear as an email address: \[local\]@\[domain\] The local value includes any string value, and the domain value includes any domain name you choose to use. We recommend using a static domain and assigning the dynamic piece of the token to the local part of the address. Use 100 characters or less for the local portion of the token. The domain value does not require an actual domain name, just a value that passes email validation.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_example.png)

Example

- t1234@example.com
- 243u1\[p9m@example.com
- T\_23r21r@example.com

For a sample token such as e\_6843846284@example.com, use example.com for all records. e\_6843846284 represents the unique identifier.

## Phone Numbers

Tokens for phone numbers cannot exceed 15 characters (alphanumeric) to pass phone number validation during import and sending phases. Use any non-empty, case-sensitive string as a token. The token does not include the country code. Provided or import the country code as a clear attribute outside of the token resolution process. If you plan on using Triggered Sends (messageContact API), provide the real country in front of the mobile token. The entire value must not exceed 15 characters.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_example.png)

Example

- 112233445566778
- a1b2c3d4e5f6g7h

For Journey Builder sends, the phone token must meet these criteria.

- Start with the numeric country code
- Contain only numbers
- Contain 15 or fewer characters

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_example.png)

Example

- 6512345678 (Singapore)
- 123456789 (United States)