The Tokenized Send feature allows clients to send Emails and SMS messages without storing sensitive personal information such as names, surnames, email addresses, or phone numbers. Instead, encoded or tokenized data is used, ensuring privacy and security while maintaining the ability to send personalized communications.

Tokenized Data Formats

Email Format

Tokenized email addresses should follow this structure: [tokenizedValue]@[domain]
tokenizedValue: Any string value.
domain: Any domain chosen by the user.

Examples:

encrypteddata@customerdomain.com

xyz_1233@static.com

098f6bcd4621d373cade4e832627b4f6@dengage.com

encrypteddata@customerdomain.com

xyz_1233@static.com

GSM Number Format

Tokenized phone numbers can include any numeric characters, with a limit of 20 characters. The + symbol is allowed.

Examples:

1234567890
+901234567890123456789
000345345333322

Sending Tokenized Requests

API Requirements

Authorization Options:
Basic Auth: Include API URL, username, and password.
API Key: Include the key-value pair in the request header.

Using GZip for Efficiency (Recommended)

For the request and response:
Set the header "Content-Encoding" to "gzip".
Set the header "Content-Type" to "application/octet-stream".

This ensures that both the request and response are properly encoded and decoded using gzip compression.
If these details have been previously saved in the system, the current values will be displayed to the user. Users can update any of the fields on the definition detail page.

📘
Important Notes
Batch Processing: Each request can handle up to 10,000 tokens and returns a response within 90 seconds.
Segment Usage: If you analyze segments with tokenized data, the system does not provide real data, only numerical results.
Reporting: Send reports will be available, but detailed domain distribution (e.g., specific email domains) cannot be provided as the actual email data is unknown to the system.