Inline authoring migration overview

Adobe Journey Optimizer is releasing a new feature which improves the way you author content for Journey Optimizer channels (email, push, SMS). As a Journey Optimizer practitioner, you now create and author your messages directly from a journey.

This feature requires a migration of existing journeys that are using messages. In this page, you will find the necessary information about this change as well as the steps that are required from you.

For more information on your roles and responsibilities as a Journey Optimizer practitioner, refer to this page.

Key take-aways

  • Am I impacted: you are impacted if you create messages from the Messages menu in the left navigation and use them in your journeys. If you are using a third-party system (such as Adobe Campaign), you are not impacted by this migration.

  • Product changes: at GA (July 25), your channel content is created and managed within each journey. The Messages menu, in the left navigation is no longer available (learn more). We will proceed to a migration for your existing journeys.

  • Timeline: migration occurs for each region at night-time, through several iterations.

  • Required actions: an automatic conversion of journeys is performed for you. That said, we need your help with a few steps. Learn more on the required steps in this page.

  • Deprecation: after the 6th of September, all journeys still using legacy messages are stopped and will be deleted later.

Benefits and product changes

Adobe’s vision is to simplify the product continuously to provide efficient and optimized user flows. This new way of creating messages brings a more streamlined user process.

We designed this new workflow to centralize content in one place, directly where it is used.

The creation of content is now performed directly inside the journey. The immediate benefits you get are:

  • Faster journey building using Journey Optimizer channels in a single flow.
  • Quick visualization of content by switching seamlessly between all email, push and SMS content in a journey.
  • Improved flow for emails and push using contextual personalization from the canvas.
  • Journey reporting centralizes detailed channel reporting information.

Here are the product changes brought by this new feature:

Before migration After migration

Before, you created your message from the Messages menu.

Now, the Messages menu, in the left navigation is no longer available.

You then created a journey, added a Message activity and selected the previously created message.

You now simply add the desired channel action activity (email, SMS, push) to your journey. In the activity, you directly configure the message parameters and access the content editor.

Before, reporting was accessible both at message and journey levels. You had to navigate between the message execution tab and the journey report.

All reporting is now centralized at journey level. This improves navigation and user experience. When you have multiple emails in a journey, you can use the Action drop-down menu to view the related report.

At GA (July 25), this new user flow applies to all new journeys. The Messages menu, in the left navigation is no longer available.

Migration timeline

A migration is required to turn your existing journeys using Messages into journeys with inline authored actions. An automatic conversion of journeys is performed for you. That said, we need your help with a few steps.

Migration occurs for each region at night-time, through several iterations. Here is the migration timeline:

  • July 25, 2022: GA - 1st iteration
  • August 1st, 2022: 2nd iteration
  • September 5th, 2022: 3rd iteration
  • September 6th, 2022: deprecation

Why do we need multiple iterations?

During an iteration, we go through each journey and migrate them when possible. There are cases where we don’t want to migrate automatically: when the journey is live (meaning there can still be profiles in it). In these cases, we ask you to perform an action and then the next iteration will migrate these journeys that couldn’t be migrated in previous iteration.

FAQ

How will I be informed of the change?

Adobe communicates with you before the first iteration.

The change is deployed overnight, through several iterations. Learn more on iterations.

You are also informed by in-product notifications, displayed on Journeys screens:

  • Before change deployment

  • During an iteration

  • After an iteration

    After an iteration, the Check status button is displayed. This allows you to view all your journeys in JSON format and their respective migration status. See this section.

  • When the banner disappears, you are good to go. No more action is required from you.

What is the migration process?

Migration is fully automatic for journeys that are not live or closed. We do not want to impact live or closed journeys to avoid any production impact. We ask you to publish the new version that we created for you.

All sandboxes of a customer ORG are processed simultaneously. During the change deployment, the following actions are performed:

ANY journey not using messages

These are not affected by the change. Only journeys using messages are targeted by the migration. However, you will still be able to access messages that are not used in a journey via the following URL: https://experience.adobe.com/#/@[ORG]/sname:[SANDBOX]/journey-optimizer/messages/

DRAFT journeys using at least one message

Draft versions of messages are modified during the migration. They do not reference a message anymore. The Message activities are replaced with the appropriate channel action activities. Each of them include the channel parameters and content.

As usual, test your draft journey before publishing it.

LIVE journeys using at least one message

The live version of a journey keeps running to avoid any production impact.

A new draft version of this journey is created during migration. This new draft version is a copy of your live version but messages are replaced with inline authored channel actions. Each channel action activity include the channel parameters and content. Content is not lost. Reporting is not lost.

We expect you to review this draft version, test it and publish it so that this becomes the live version.

FINISHED or STOPPED journeys using at least one message

These journeys are migrated too.

When looking at the journey report, reports are now richer and include the level of information that was previously available in message report.

CLOSED journeys using at least one message

The closed version of a journey keeps running for any profile inside, to avoid any production impact.

Closed journeys are automatically switched to the “Finished” status after 30 days. They will be taken into account in the next iteration, when they are finished.

Multi-channel journeys

These are not migrated. You have to re-create them.

What are my action items as a customer?

An automatic conversion of journeys is performed for you but a few steps are required. Learn more on the required steps in this page.

How can I check the migration status?

Click the Check status button in the top banner. The following page is displayed.

The status report is at sandbox level. This report includes several useful sections:

migrationStatus

This section displays the migration information since the first iteration. Numbers are incremented after each iteration.

  • MIGRATED: number of draft, finished and stopped journeys migrated successfully.
  • NEW_VERSION_CREATED: number of live journeys migrated. For each live journey, a new draft version is created: you must test and publish this version.
  • ERROR: number of draft, finished and stopped journeys not migrated because of a failure. You need to re-create them.
  • ERROR_ON_NEW_VERSION_CREATION: number of live journeys not migrated because of a failure. new draft journey versions not migrated because of a failure. New draft versions have not been created for them. You need to re-create them manually.

eligibilityStatus

This section lists the remaining items after the last iteration:

  • toMigrate: number of draft, finished and stopped journeys that need to be migrated.
  • createNewVersion: number of live journeys to migrate.
  • noMigration_live: number of live journeys that do not need to be migrated. Closed journeys are also listed here.
  • noMigration: number of journeys that do not need to be migrated.

The details section gives, for each of the above sections, the list of related journeys.

Will this change cause any interruption of service?

There will be no interruption of service.

  • On live journeys: no impact, they keep running.
  • On authored journeys: during migration (at night-time), we strongly recommend not to create, edit or delete journeys.

Will there be loss of data?

There will be no data loss and no impact on live journeys. You will be in control of publishing updated journey versions.

Will there be loss of functionality?

There will be a change in the way you author message. There will be no loss of functionality.

Will there be access to the environment during the migration process?

Migration occurs at night-time. You will be able to use the product. But do not create, edit or delete journeys.

Will the messages continue to be sent?

Yes, live journeys keep running.

How do I know that the migration is complete?

The migration is complete when the banner disappears. See this section.

The Inline authoring feature will impact permissions. Every Message related permission, such as View Messages or Manage Messages, will be automatically included in the permissions linked to the Journeys capability.

Learn more in this page.

On this page