Email Activity in Journey Builder

Considerations

• Each journey version has its own triggered send for each email activity. A new triggered send is created when a new journey version is activated.
• Triggered send validation compares the email's personalization strings to event data from the journey entry source. Entry source event data contains the field names and corresponding data types in the journey's entry source data extension.
• Update email properties, such as Send Classifications or Publication Lists, by editing the email activity.
• Update images, content, and other Email Studio-related components by pausing, publishing changes, and restarting the triggered send.
  • Dynamic subject rules
  • Send classifications
  • Sender profiles
  • Delivery profiles
  Journey Builder email activities that use the email don’t automatically receive these updates. Implement changes to emails by updating each email activity while in draft mode, then reactivating the journey. Alternately, update the send on the classic Journey Builder Sends page.
• When validation errors occur, make sure the email's personalization strings are calling data values included in the entry source data extension. If the email personalization includes a field that isn’t in the entry source data extension, email validation can fail.
• Emails using AMPscript can use the Data Extension Lookup() function to interact with data extensions in your account.
• Emails using AMPscript for personalization aren’t required to call data values found in the event source data extension.