---
schema_version: "1"
id: e51640599de54ffa34d005014b27f57ca38daf640deb36ee10e0c40bb1adc317
title: Tokenized Send Examples for Marketing Cloud Engagement
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_send_examples.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_send_examples.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a00c7b48594302efb05e6eea0062b24a5df9bdcb2fcfd0ada38825938d3b4509
description: View examples of Email Send and MobileConnect Send and Stop in Marketing Cloud Engagement.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Tokenized Send Examples for Marketing Cloud Engagement

View examples of Email Send and MobileConnect Send and Stop in Marketing Cloud Engagement.

## Email Send

This example demonstrates an email send using Tokenized Sending in Marketing Cloud Engagement.

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

(1) Contact information is stored in the customer data warehouse.

(2) Tokens are imported before a send.

(3) User initiates a send. Content building occurs now.

(4) Marketing Cloud Engagement initiates a call to the customer data warehouse for contact information.

(5) Customer data warehouse returns contact information.

(6) Marketing Cloud Engagement uses returned contact information for send.

## MobileConnect Send

This example demonstrates using Tokenized Sending for a MobileConnect Send in Marketing Cloud Engagement.

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

(1) Contact information is stored in the customer data warehouse.

(2) Tokens are imported before a send.

(3) User initiates a send. Content building occurs now.

(4) Marketing Cloud Engagement initiates a call to the customer data warehouse for contact information.

(5) Customer data warehouse returns contact information.

(6) Marketing Cloud Engagement uses returned contact information for send.

## MobileConnect STOP

This example demonstrates Tokenized Sending for a MobileConnect STOP request in Marketing Cloud Engagement.

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

(1) Contact sends a STOP SMS message.

(2) Marketing Cloud Engagement initiates a call to the customer data warehouse with the mobile number used to send the STOP message.

(3) Customer data warehouse returns a token value.

(4) Marketing Cloud Engagement receives the token value linked to the mobile number.

(5) The contact record is updated if available. If no token is returned, Marketing Cloud Engagement stores the value for customer review.