You are here:
Marketing Cloud Connect Triggered Sends
Automatically send relevant, timely, personalized messages using triggered sends. Welcome emails to new customers or thank you notes for purchases are examples of how triggered sends are commonly used. Review important prerequisites and learn how to effectively use triggered sends with Marketing Cloud Connect for Marketing Cloud Engagement.
Create triggered sends on objects with a lookup to a Contact ID or Lead ID, or to an Account object if person accounts are enabled. After you create a trigger for each object, messages are sent each time an update or insert event occurs on the objects.
You can use many features of triggered sends within the Sales or Service Cloud.
- Create and edit triggered sends.
- View existing triggered sends across clouds.
- Review aggregate tracking data for triggered sends across clouds.
- Add subscribers to specific data extensions for more marketing opportunities. If no destination data extension is selected, the subscriber is added to the All Subscribers list in Engagement. If the user that activated the send doesn’t have access to the All Subscribers list, the contact or lead isn’t added to that list.
Before you begin…
- Acquire access to the All Subscribers list in Engagement.
- Ensure that triggered sends are enabled in Engagement.
- Set up send classifications in Engagement for triggered sends. If needed, overwrite send classifications in Marketing Cloud Connect using Override from Name/Email Address.
- The email associated with the triggered send must pass validation in Engagement.
- Triggered sends only work with events that occur after updates and inserts.
- To change the filter criteria or select a new email for your triggered send after creating it through Marketing Cloud Connect, update the triggered send in Sales or Service Cloud. Editing a triggered send in Engagement after creating it in Sales Cloud changes the ID associated with the triggered send, which prevents updates.
- Triggered sends use Apex code. Write and test triggers in a Salesforce developer environment, sandbox, or trial org before publishing to production.
- Triggered sends don’t support bulk updates or inserts.
- Marketing Cloud Connect is governed by SOQL query limits. Each evaluation of a triggered send uses one query toward the SOQL limit of 100 at one time. To reduce the number of queries performed, use the automateByName Apex method.
- You can execute up to 50 triggered sends within a transaction, including a bulk record update or sends that meet filter criteria for a single record.
