Create message presets

With Journey Optimizer, you can set up message presets that define all the technical parameters required for email and push notification message: email type, sender email and name, mobile apps, and more.

CAUTION
  • Message presets configuration is restricted to Journey Administrators. Learn more

  • You must perform Email configuration and Push configuration steps before creating message presets.

Once message presets have been configured, you be able to select them when creating messages from the Presets list.

➡️ Learn how to create and use email presets in this video

Create a message preset

To create a message preset, follow these steps:

  1. Access the Channels > Branding > Message presets menu, then click Create Message preset.

  2. Enter a name and a description (optional) for the preset, then select the channel(s) to configure.

    NOTE

    Names must begin with a letter (A-Z). It can only contain alpha-numeric characters. You can also use underscore _, dot. and hyphen - characters.

  3. Configure the email settings.

    • Select the type of message that will be sent with the preset: Transactional or Marketing

      CAUTION

      Transactional messages can be sent to profiles who unsubscribed from marketing communications. These messages can only be sent in specific contexts, such as password reset, order status, delivery notification for example.

    • Select the subdomain to use to send the emails. Learn more

    • Select the IP pool to associate with the preset. Learn more

    • Enter the header parameters for the emails sent using that preset.

      CAUTION

      Email addresses must use the current selected delegated subdomain.

      • Sender name: The name of the sender, such as your brand’s name.

      • Sender email: The email address you want to use for your communications. For example, if the delegated subdomain is marketing.luma.com, you can use contact@marketing.luma.com.

      • Reply to (name): The name that will be used when the recipient clicks the Reply button in their email client software.

      • Reply to (email): The email address that will be used when the recipient clicks the Reply button in their email client software. You must use an address defined on the delegated subdomain (for example, reply@marketing.luma.com), otherwise the emails will be dropped.

      • Error email: All errors generated by ISPs after a few days of mail being delivered (asynchronous bounces) are received on this address.

      NOTE

      From the October 2021 release, it is not possible anymore to define a forward email addresse from the Journey Optimizer user interface. If you want all emails received by Journey Optimizer for the delegated subdomain to be forwarded to a specific email address, contact the Adobe Customer Care Support Team.

      NOTE

      Names must begin with a letter (A-Z). It can only contain alpha-numeric characters. You can also use underscore _, dot. and hyphen - characters.

    • Configure the email retry parameters. By default, the retry time period is set to 84 hours, but you can adjust this setting to better suit your needs.

      You must enter an integer value (in hours or minutes) within the following range:

      • For marketing email type, the minimum retry period is 6 hours.
      • For transactional email type, the minimum retry period is 10 minutes.
      • For both email types, the maximum retry period is 84 hours (or 5040 minutes).
  4. Configure the push notification settings.

    • Select at least one platform: iOS and/or Android

    • Select the mobile applications to use for each platform.

      For more on how to configure your environment to send push notifications, refer to this section.

  5. Once all the parameters have been configured, click Submit to confirm. You can also save the message preset as draft and resume its configuration later on.

  6. Once the message preset has been created, it displays in the list with the Processing status.

    During this step, several checks will be performed to verify that it has been configured properly. The processing time is around 48h-72h, and can take up to 7-10 business days.

    These checks include deliverability tests that are performed by Adobe deliverability team:

    • SPF validation
    • DKIM validation
    • MX record validation
    • Check IPs denylisting
    • Helo host check
    • IP pool verification
    • A/PTR record, t/m/res subdomain verification
    NOTE

    If the checks are not successful, learn more on the possible failure reasons in this section.

  7. Once the checks are successful, the message preset gets the Active status. It is ready to be used to deliver messages.

Monitor message presets

All your message presets display in the Channels > Message presets menu. Filters are available to help you browse through the list (channel type, user, status).

Message presets can have the following statuses:

  • Draft: The message preset has been saved as a draft and has not been submitted yet. Open it to resume the configuration.
  • Processing: The message preset has been submitted and is going through several verifications steps.
  • Active: The message preset has been verified and can be selected to create messages.
  • Failed: One or several checks have failed during the message preset verification.
  • Deactivated: The message preset is deactivated. It cannot be used to create new messages.

In case a message preset creation fails, the details on each possible failure reason are described below.

If one of these errors occurs, contact the Adobe Customer Care Support Team to get assistance.

  • SPF validation failed: SPF (Sender Policy Framework) is an email authentication protocol that allows to specify authorized IPs that can send emails from a given subdomain. SPF validation failure means that the IP addresses in the SPF record do not match the IP addresses used for sending emails to the mailbox providers.

  • DKIM validation failed: DKIM (DomainKeys Identified Mail) allows the recipient server to verify that the received message was sent by the genuine sender of the associated domain and that the content of the original message was not altered on its way. DKIM validation failure means that the receiving mail servers are unable to verify the authenticity of the message content and its association with the sending domain.:

  • MX record validation failed: MX (Mail eXchange) record validation failure means that the mail servers responsible for accepting inbound emails on behalf of a given subdomain are not correctly configured.

  • Deliverability configurations failed: Deliverability configurations failure can happen due to any of the following reasons:

    • Blocklisting of the allocated IPs
    • Invalid helo name
    • Emails being sent from IPs other than the ones specified in the IP pool of the corresponding preset
    • Unable to deliver emails to inboxes of major ISPs like Gmail and Yahoo

Edit a message preset

To edit a message preset, follow the steps below.

NOTE

You cannot edit the Push notification settings. If a message preset is only configured for the Push notification channel, it is not editable.

  1. From the list, click a message preset name to open it.

  2. Edit its properties as desired.

    NOTE

    If a message preset has the Active status, the Name, Select channel and Subdomain fields are greyed out and cannot be edited.

  3. Click Submit to confirm your changes.

    NOTE

    You can also save the message preset as draft and resume update later on.

Once the changes are submitted, the message preset will go through a validation cycle similar to the one in place when creating a preset.

NOTE

If you only edit the Description, Email type and/or Email retry parameters fields, the update is instantaneous.

For message presets that have the Active status, you can check the details of the update. To do so:

  • Click the Recent update icon that is displayed next to the active preset name.

  • You can also access the update details from an active message preset while update is in progress.

On the Recent update screen, you can see information such as the update status, and the list of requested changes.

Update statuses

A message preset update can have the following statuses:

  • Processing: The message preset update has been submitted and is going through several verifications steps.
  • Success: The updated message preset has been verified and can be selected to create messages.
  • Failed: One or several checks have failed during the message preset update verification.

Each status is detailed below.

Processing

Several deliverability checks will be performed to verify that the preset has been updated properly.

NOTE

If you only edit the Description, Email type and/or Email retry parameters fields, the update is instantaneous.

The processing time is around 48h-72h, and can take up to 7-10 business days. Learn more on the checks performed during the validation cycle in this section.

If you edit a preset that was already active:

  • Its status remains Active while the validation process is in progress.

  • The Recent update icon displays next to the name of the preset in the message presets list.

  • During the validation process, the messages configured using this preset are still using the older version of the preset.

NOTE

You cannot modify a message preset while update is in progress. You can still click its name, but all the fields are greyed out. The changes will not be reflected until the update is successful.

Success

Once the validation process is successful, the new version of the preset is automatically used in all messages using this preset. However, you may have to wait:

  • a few minutes before it is consumed by the unitary messages,
  • until the next batch for the preset to be effective in batch messages.

Failed

If the validation process fails, the older version of the preset will still be used.

Learn more on the possible failure reasons in this section.

Upon update failing, the preset becomes editable again. You can click its name and update the settings that need to be fixed.

Deactivate a message preset

To make an Active message preset unavailable to create new messages, you can deactivate it. However, the published messages using this preset will not be affected and will continue working.

NOTE

You cannot deactivate a message preset while an update is processing. You must wait until the update is successful or has failed. Learn more on editing message presets and on the update statuses.

  1. Access the message presets list.

  2. For the active preset of your choice, click the More actions button.

  3. Select Deactivate.

NOTE

Deactivated message presets cannot be deleted to avoid any issue in journeys using these presets to send messages.

You cannot directly edit a deactivated message preset. However, you can duplicate it and edit the copy to create a new version that you will use to create new messages. You can also activate it again, and wait until the update is successful to edit it.

How-to video

Learn how to create message presets, how to use them and how to delegate a subdomain and create an IP pool.

On this page