Before creating triggered emails, the following steps must be completed. These steps are technical and may require a web developer.
- Implement Events and Cart State
- Identify the User On-Site Using a Hashed Email
- Recipient List Management and Sync
- Unsubscribe Handling
- ESP Integration
Implement Events and Cart State
Make sure the following two items are implemented.
- eCommerce Events
- Add to Cart (with cart parameter)
- Remove from Cart (with cart parameter)
- Sync Cart State
In order for Dynamic Yield to know the user’s cart content this has to be reported from the site using add and remove from cart events, or sync cart events. For details, see Events for Web.
Identify the User On-Site
This is used to associate a Dynamic Yield generated user ID for all site visitors (DYID) with a hashed email address or external ID as a cross channel Customer ID (CUID). There are two methods for doing this:
- Using the identify schema events (login, signup, and newsletter subscription). For details, see Events for Web.
- Adding a hashed email as a URL parameter in all email links (recommended). Once this is added, a Custom Action added to the site can capture the hashed email from the site URL and trigger an Identify API call.
Recipient List Management and Sync
Dynamic Yield must have a list of users who are eligible (opted-in) to receive triggered emails and/or be included in exported audience data. You maintain this list outside of Dynamic Yield, and synchronize a copy to us using one of the following methods:
- Using a User Email Data Feed. These data feeds are built from a CSV file stored in an Amazon S3 bucket provided to each customer.
- Using message opt-in and message opt-out events. In order to use this method, a one-time manual upload of existing recipients via CSV is required to initially populate the recipient list.
These events involve passing plain-text emails which are considered private data. While Dynamic Yield complies with security aspects in the transfer and persistence of this data, firing this event should be executed according to local law.
You should only use one method at a time, as the User Email Feed will override any information received from message opt-in and out events. Dynamic Yield maintains the recipient list in a dedicated personal data compliant storage.
We recommend enabling users to unsubscribe directly from your triggered emails. To do this, add a link in the HTML of your triggered email variations or templates that directs them to the unsubscribe functionality of your recipient list management software.
To maintain our copy of the recipient list above, you need to update the list in Dynamic Yield depending on which method you used above (API or CSV file).
- If you are using the APIs, send a message opt out call as described above
- If you are using a User Email Data Feed, delete the email from the source file and the user will be opted out during the next data feed synchronization.
To learn how to integrate your ESP, refer to one of the articles below.
- Bronto (early access)
- Listrak (early access)
- Custom ESP (any ESP using restful APIs)
If you do not have one of the above ESPs and you cannot use the custom ESP integration, Dynamic Yield can send emails on your behalf. Each customer can receive a dedicated IP and warm-up can be supported upon request.
For details, contact your Customer Success Manager. They will provide you with sender authentication and reverse DNS entries that you will need to update in your DNS host provider.
Note: You can only enable one integration for triggered emails. If you want to switch to a different ESP, you will need to delete any existing triggered email campaigns.