Prerequisites and guardrails web-prerequisites

To be able to access and author web pages in the Journey Optimizer user interface, follow the prerequisites below:

  • To add modifications to your website, you need to have a specific implementation. Learn more

  • To access the Journey Optimizer web designer, you must have a specific Google Chrome browser extension installed. Learn more

  • For the web experience to be delivered correctly, make sure you define the Adobe Experience Platform settings detailed here.

Caution notes caution-notes-web

  • Currently in Journey Optimizer you can only create web experiences in campaigns. Learn more

  • Journey Optimizer web campaigns target new profiles that have not been engaged before on other channels. This will increase your total engageable profile count, which may have cost implications if the contractual number of engageable profiles you purchased is exceeded. Licence metrics for each package are listed on the Journey Optimizer Product Description page.

For now, Web channel is not available for organizations that have purchased the Adobe Healthcare Shield and Privacy and Security Shield add-on offerings.

Implementation prerequisites implementation-prerequisites

Currently two types of implementations are supported to enable authoring and delivery of web channel campaigns on your web properties:

  • Client-side only – To add modifications to your website, you need to implement the Adobe Experience Platform Web SDK on your website.

    note note
    Make sure your AEP Web SDK version is 2.16 or above.
  • Hybrid mode – You can use the AEP Edge Network Server API to request for personalization server-side; the response is provided to the Adobe Experience Platform Web SDK to render the modifications client-side. Learn more in the Adobe Experience Platform Edge Network Server API documentation. You can find out more about the hybrid mode and check some implementation samples in this blog post.

The server-side only implementation is not currently supported.

Visual authoring prerequisites visual-authoring-prerequisites

To be able to open, author and preview your web pages reliably into the Journey Optimizer web designer, you must have the Adobe Experience Cloud Visual Editing Helper browser extension installed on your web browser.

Google Chrome and Microsoft Edge are currently the only browsers that support authoring web pages in Journey Optimizer.

Install the Visual Editing Helper extension install-visual-editing-helper

To download and install the Visual Editing Helper browser extension, follow the steps below.

  1. Open a new tab in your browser (Google Chrome or Microsoft Edge).

  2. Go to the Google Chrome Web Store.

  3. If you are using Microsoft Edge, select Allow extensions from other stores on the top banner. This will allow you to add extensions from the Chrome Web Store to Microsoft Edge.

  4. Search and navigate to the Adobe Experience Cloud Visual Editing Helper browser extension.

  5. Click Add to Chrome > Add Extension.

    note note
    If you are using Microsoft Edge, this will add the extension to Edge even though the button is labelled Add to Chrome.
  6. Make sure the Visual Editing Helper browser extension is correctly enabled in your browser’s toolbar.

The Adobe Experience Cloud Visual Editing Helper is now automatically enabled when a website is opened in the Journey Optimizer web designer to power authoring.

The extension does not have any conditional settings and handles all the settings automatically, including SameSite cookies settings.

Some websites might not open reliably in the Journey Optimizer web designer due to one of the following reasons:
  • The website has strict security policies.
  • The website is in an iframe.
  • The customer’s QA or stage site is not available to the outside world (the site is internal).

Troubleshoot website not loading troubleshooting

When using the Adobe Journey Optimizer web designer, if you attempt to load a website that fails to load, a message displays suggesting that you install the Visual Editing Helper browser extension.

  1. Make sure the Visual Editing Helper browser extension is correctly installed.

  2. If the website still behaves unexpectedly, make sure third-party cookies are allowed in your browser, otherwise the web page cannot be loaded inside the Journey Optimizer web designer.

For pages under authentication, if the login page fails to load, or if after trying to log in you are still not logged in:

  1. Try to log in first in a new browser tab and navigate to the desired page, then copy the URL and try to open it in the Journey Optimizer web designer.

  2. If you still cannot load your website in the Journey Optimizer web designer, contact Adobe Customer Care to report the problem, making sure you specify the failing URL.

Delivery prerequisites delivery-prerequisites

For the web experience to be delivered correctly, the following settings must be defined:

  • In the Adobe Experience Platform Data Collection, make sure you have a datastream defined such as under the Adobe Experience Platform service you have the Adobe Journey Optimizer option enabled.

    This ensures that the Journey Optimizer inbound events are correctly handled by the Adobe Experience Platform Edge. Learn more

  • In Adobe Experience Platform, make sure you have one merge policy with the Active-On-Edge Merge Policy option enabled. To do this, select a policy under the Customer > Profiles > Merge Policies Experience Platform menu. Learn more

    This merge policy is used by Journey Optimizer inbound channels to correctly activate and publish inbound campaigns on the edge. Learn more

  • To troubleshoot the delivery of Journey Optimizer Web experiences, you can use the Edge Delivery view within Adobe Experience Platform Assurance. This plugin enables you to inspect request calls in detail, verify whether the expected edge calls occur as anticipated, and examine profile data, including identity maps, segment memberships, and consent settings. Additionally, you can review the activities the request qualified for and identify those it did not.

    Using the Edge Delivery plugin helps you gain the insights needed to understand and troubleshoot your inbound implementations effectively.

    Learn more on Edge Delivery view

Content experiment prerequisites experiment-prerequisites

To enable content experiments for the web channel, you need to make sure the dataset used in your web implementation datastream is also included in your reporting configuration.

In other words, when configuring experiment reporting, if you add a dataset that is not present in your web datastream, web data will not display in the content experiment reports.

Learn how to add datasets for content experiment reporting in this section.

The dataset is used read-only by the Journey Optimizer reporting system and doesn’t affect data collection or data ingestion.

If you are not using the following pre-defined field groups for your dataset schema: AEP Web SDK ExperienceEvent and Consumer Experience Event (as defined in this page), make sure to add the following field groups: Experience Event - Proposition Interactions, Application Details, Commerce Details, and Web Details. These are needed by the Journey Optimizer content experiment reporting as they are tracking which experiments and treatments each profile is participating in.

Adding these field groups doesn’t impact the normal data collection. It is additive only for the pages where an experiment is running, leaving all the other tracking untouched.

Branded domains for assets branded-domains-for-assets

When authoring web experiences, if you add content coming from the Adobe Experience Manager Assets library, you must set up the subdomain that will be used to publish this content. Learn more