---
schema_version: "1"
id: 08088957cb000e1a225b2264b274451faf1d045ad5e2b91e67d664fc17c36711
title: Encrypt Triggered Send Data from Sales Cloud and Service Cloud
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_error_resolution_triggered_sends.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_error_resolution_triggered_sends.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 839c8032320af1104a47d3c21fe10871d7c32f3e4b0d36879fa6aa0d30be8139
description: Ensure that triggered sends from Sales Cloud or Service Cloud insert encrypted data into the All Subscriber List in Marketing Cloud Engagement.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Encrypt Triggered Send Data from Sales Cloud and Service Cloud

Ensure that triggered sends from Sales Cloud or Service Cloud insert encrypted data into the All Subscriber List in Marketing Cloud Engagement.

When you create a triggered send in Sales Cloud, Marketing Cloud Engagement creates a triggered send definition. You can view the triggered sends in the Interactions menu in Email Studio. The corresponding triggered send uses the same name as the triggered send created in Sales Cloud or Service Cloud.

Edit the triggered send definition in Marketing Cloud Engagement to write to an encrypted data extension created using a triggered send email template data extension. To properly encrypt the data in both Sales Cloud and Marketing Cloud Engagement, publish the changes and restart the triggered send.