Get started with code-based channel

Journey Optimizer allows you to personalize and test the experiences you want to deliver to your customers across all your touchpoints like: web apps, mobile apps, desktop apps, video consoles, TV connected devices, smart TVs, kiosks, ATMs, voice assistants, IoT devices, etc.

With the code-based experience capability, you can define inbound experiences using a simple and intuitive non-visual editor. It allows you to insert and edit specific elements at individual and more granular locations of your apps or web pages, no matter the type of applications you have - rather than applying modifications to an entire content.

How it works

Guardrails and prerequisites

Code-based channel configuration

Create a code-based experience

➡️ An end-to-end use case showing how to use content experiments to compare decisions with the code-based experience channel is presentend in this section.

When to use code-based vs. other channels

Code-based vs. other channels

When to use the code-based channel rather than the other Journey Optimizer channels?

• You can consider using code-based experiences any time when your digital property is not accessed through a web browser or a mobile app – cases in which you can probably better use the Journey Optimizer web channel or the Journey Optimizer in-app messaging channel.

• You can use the code-based channel as an alternative to the Journey Optimizer web or in-app channels in case you have an API-based, headless or server-side implementation.

• You can also leverage the code-based channel on native mobile applications as an alternative to the in-app channel if you want to modify the content inside your native app instead of showing modals, popups or overlays.

Code-based vs. web channel

To execute web use cases, you can use either the web channel or code-based experience, but depending on your context one would be more appropriate than the other. The main differences are listed below so you can make an informed decision on what to use, and when.

Web

• Edit your content using the web designer visual editor or the web non-visual editor.
• You need the Adobe Experience Platform Web SDK – a client-side implementation.

• The web channel lets you modify everything on your page and has a pre-defined list of actions you can use to make changes. Learn more
• It is easy to set up and get going fast.
• It is marketer-persona focused.

Code-based experience

• Edit your content using the personalization editor.
• You need either the Adobe Experience Platform Web SDK – client-side implementation, or the the AEP Edge Network Server API – server-side implementation.
• The code-based experience requires previous development work on your implementation to make sure that your applications can interpret and deliver the content published on the edge by Journey Optimizer for these locations. Learn more
• It requires more planning and it can change only the things that developers specify. Therefore, it is essential to identify the components (home banner, hero image, menu bar, etc.) on the applications that need to be modified for personalization or testing, and work with your development team to build the implementation needed for handling these changes.
• It allows you to use JSON code content.
• It is developer-persona focused.

How it works

To edit your content using the Journey Optimizer code-based experience feature, your pages or apps need to be instrumented. To do so, you must declare upfront the specific individual locations (called “surfaces”) where you want to insert or replace content.

The key steps to create and deliver a code-based experience are as follows.

1. Make sure you follow the channel-specific prerequisites. Learn more

2. Define a surface in your application implementation, which is basically the location where you want to add your experience.

3. Create a code-based channel configuration that references that location. Learn how

4. Create a journey or campaign in Journey Optimizer using this configuration. Learn how

5. Compose an experience by specifying content for the selected configuration using the Journey Optimizer personalization editor. Learn how

6. Test your code-based experience. Learn how

7. Publish it. Learn how

8. Once your code-based experience journey or campaign is live, the app or page implementation that requests content for the surface must be in place for the content to be retrieved and displayed.

   INFO

   To ensure this, your app implementation team makes explicit API or SDK calls to fetch content for the surface defined in the code-based configuration, such as “Banner Text” or “Recommendations Tray 1”, or non-UI-related decision points in an application, such as “search algorithm parameters”. Learn more