Documentation Journey Optimizer Journey Optimizer Guide

Configure your web experiences

Last update: April 7, 2025

CREATED FOR:

Experienced
Admin

Create a web channel configuration

A web configuration is a web property identified by a URL where the content will be delivered. It can match a single page URL or multiple pages, allowing you to deliver modifications across one or several web pages.

To create a web channel configuration, follow the steps below.

Access the Channels > General settings > Channel configurations menu, then click Create channel configuration.
Enter a name and a description (optional) for the configuration.

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.
To assign custom or core data usage labels to the configuration, you can select Manage access. Learn more about Object Level Access Control (OLAC)
Select the Web channel.
Select Marketing action(s) to associate consent policies to the messages using this configuration. All consent policies associated with the marketing action are leveraged in order to respect the preferences of your customers. Learn more
In the Web settings section, select one of the following options:
- Single page - If you want to apply the changes to a single page only, enter a Page URL.
- Pages matching rule - To target multiple URLs matching the same rule, build a pages matching rule, and enter a Default authoring and preview URL. Learn more
Click Submit to save your changes.

You can now select this configuration when using the Web channel in your campaigns or journeys.

Build a pages matching rule

When creating a web or code-based experience configuration, you can build a Pages matching rule to target multiple URLs matching the same rule. You can therefore apply the same content changes across multiple pages at once.

For example, you may want to apply the changes to a hero banner across a whole website, or add a top image that displays on all the product pages of a website.

When configuring your web or code-based experience, select Pages matching rule.
Define your criteria for the Domain and Page fields.

NOTE
Check the available operators in this section.

For example, if you want to edit elements that are displayed on all the women product pages of your Luma website, select Domain > Starts with > luma and Page > Contains > women.
If your use case cannot be modeled using one rule, you have the option to add multiple rules. Click Add another page rule and repeat the step above.

NOTE
You can add up to 10 rules.
You can use the Or or Exclude operators between the different rules.

Exclude is useful when one of the pages that match the rule defined should not be targeted. For example, you can target all luma.com pages that contain product, excluding the following page: https://luma.com/blogs/productinfo.
Enter the Default authoring and preview URL. This step ensures that the pages generated or matched by the rule have a designated URL for both content creation and preview purposes.

Available operators for building page matching rules

When creating a rule that matches multiple pages, you can use different operators on the Domain and on the Path sections to build your desired rule. The available operators are listed below.

Domain

Operator
Description
Examples
Equals
Exact match of the domain.
Starts with
Matches all the domains (including sub-domains) which start with the string entered.
Ex: “Starts with: dev” -> matches all the domains and subdomains that start with “dev”, like: dev.example.com, dev.products.example.com, developer.example.com
Ends with
Matches all the domains (including sub-domains) which end with the string entered.
Ex: “Ends with: example.com” -> matches all the domains and subdomains that ends with “example.com”, like: stage.example.com, prod.example.com, myexample.com
Wildcard matching
“Wildcard matching” operator allows the user to define a wildcard match in the middle of the the string, like “dev.*.example.com”. The validation rules are that the value must contain one and only one wildcard (asterisk) when the operator is “wildcard matching”.
Ex: “Wildcard matching: dev.*.example.com” -> matches domains like: dev.products.example.com, dev.mytest.products.example.com, dev.blog.example.com
Any
Matches all the domains – useful when testing a particular path across domains
Path

Operator

Description

Examples

Equals

Exact match of the path.

Starts with

Matches all the paths (including sub-paths) which start with the string entered.

Ends with

Matches all the paths (including sub-paths) which end with the string entered.

Any

Matches all the paths – useful when targeting all paths under one or multiple domains.

Wildcard matching

"Wildcard matching" operator allows the user to define an internal wildcard inside the path, like "/products/*/detail". The wildcard character * in Path ** component, matches any sequence of characters until the first / character is encountered. /*/ matches any sequence of characters (including sub-paths)

Ex: "Wildcard matching: /products/*/detail", matches all the paths like:

example.com/products/yoga/detail
example.com/products/surf/detail
example.com/products/tennis/detail
example.com/products/yoga/pants/detail

Ex: "Matches: /prod*/detail, matches all the paths like:

example.com/products/detail
example.com/production/detail

does not match paths like:

example.com/products/yoga/detail

Contains

"contains" gets translated to a wildcard like "mystring" and matches all the paths that contain this sequence of characters.

Ex: "Contains: product", matches all the paths that contain the string product, like:

example.com/products
example.com/yoga/perfproduct
example.com/surf/productdescription
example.com/home/product/page

recommendation-more-help