Check your message for errors and prepare it for delivery

When you're done designing and previewing your email, you're ready to start sending it. First, you need to check it for errors. Then, once it passes the error check, you must go live to activate it and make it available on the marketing services. Finally, set up a customer journey to establish the target segment, delivery schedule, and follow-up actions.

Required elements: How to pass the error check

Before you can go-live with or test-send your message, it must pass an error check. You can run an error check at any time by selecting Check for Errors on the command bar. An error check is also run automatically each time you select Go Live or Test Send.

All messages must include the following:

The following are also confirmed by the check:

  • All dynamic expressions and HTML code must compile and generate valid values.
  • All videos and images referenced from the Dynamics 365 Customer Insights - Journeys content libraries must exist.
  • The To field must be an expression (not a static value) that results in a valid email address. The customer journey that sends the message will use this expression to find the address to use for each recipient (contact) processed by the journey. The default expression provided for this ({{contact.emailaddress1}}) is usually best, but you might customize this to support custom scenarios (such as email addresses stored in another field).
  • The From address should use a domain that is authenticated and registered using DKIM as belonging to your organization. You can go live with a From address that uses an unauthenticated domain, but you'll get a warning because this isn't recommended. You can't go live with a domain that is authenticated as belonging to another organization (this generates an error). More information: Authenticate your domains

Note

Errors that result from problems with your dynamic expressions are described in detail and provide a code sample that should help you locate the problem. However, one message, which shows the text "Dynamic content references a static entity that's missing a record ID", can appear for two different reasons. The first reason is the one implied by the text, which means you included a reference to a specific record, but left out the ID of the record you want to show. The second reason (which is only loosely related to the displayed text) is that you are referencing an entity that isn't yet synced with the marketing-insights service and therefore isn't available to the error checker; to fix this, ask your admin to confirm whether the required entity is synced, and to add it if it isn't. More information: Choose entities to sync with the marketing-insights service

Go live and set up a customer journey to deliver your message

While you prepare a message, it stays in a draft state, which means that it's inactive and can't be sent. To send it, you must first go live with it (which activates its dynamic content and moves it to the bulk messaging server), and then add it to a customer journey.

To publish a message, open it and select Go Live on the command bar. Dynamics 365 Customer Insights - Journeys will run a final validation check, as described in the previous section, and—if it passes—publish the message. If errors are returned, read the error messages, address the issues, and try again until the message is successfully published.

To address, schedule and deliver the message, set up a customer journey that includes a segment tile to define the target audience and an email tile that references your live email design and delivers it to each contact that enters the tile. You can also include any number of other tiles, including triggers and follow-up actions. To run the customer journey and begin sending messages, choose a start date and end date and go live.

Important

You should limit the HTML content of email messages to a maximum size of 100KB. This size limit includes all HTML text, styles, comments, and embedded graphics (but not anchored external graphics). If the HTML content exceeds 128KB, you'll receive a size warning, but you can still go live with the email and any customer journey that includes the email.

When you go live with a message, Dynamics 365 Customer Insights - Journeys processes the HTML content to create inline styles, compress spaces, and more, so it can be hard to know the exact final size of the message. If you have a message that you suspect violates the HTML size limit, do the following:

  1. Open a web browser and enter a URL of the form: https://<your_domain>/api/data/v9.0/msdyncrm_marketingemails(<email_id>)
    Where:
    • <your_domain> is the root of your Dynamics 365 Customer Insights - Journeys instance (such as "contoso.crm.dynamics.com").
    • <email_id> is the ID for the message you want to check. To find this ID, open the message in Dynamics 365 Customer Insights - Journeys and find the value of the id= parameter shown in your browser's address bar.
  2. Search for the value of the field "msdyncrm_emailbody" in the returned JSON.
  3. Copy the value of that field into a text program that can tell you the exact size of the HTML content.

More information: Use customer journeys to create automated campaigns and Go live with publishable entities and track their status

Gain insights from your email results

Once you start delivering an email message using a customer journey, Dynamics 365 Customer Insights - Journeys will begin to collect information about how recipients interact with that message. The system provides a wealth of information, including analytics, KPIs, graphs, and more, to help you gain insights from your marketing results. More information: Analyze results to gain insights from your marketing activities