Token Formats

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.

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.

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