DocumentationJourney OptimizerJourney Optimizer Guide

Configure your web experiences web-configuration

Last update: September 8, 2026

CREATED FOR:

  • Experienced
  • Admin

On this page: Learn how to create a web channel configuration in Adobe Journey Optimizer, targeting either a single page URL or multiple pages with a pages matching rule and its available operators.

style
shade-box

Create a web channel configuration create-web-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.

  1. Access the Channels > General settings > Channel configurations menu, then click Create channel configuration.

  2. Enter a name and a description (optional) for the configuration.

    note
    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.

  3. To assign custom or core data usage labels to the configuration, you can select Manage access. Learn more about Object Level Access Control (OLAC)

  4. Select the Web channel.

  5. 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

  6. 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

  7. 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 web-page-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.

  1. When configuring your web or code-based experience, select Pages matching rule.

  2. Define your criteria for the Domain and Page fields.

    note
    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.

  3. 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
    NOTE
    You can add up to 10 rules.

  4. 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.

  5. 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 available-operators

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

    table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3
    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
AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

  • TL;DR: This page explains how to create a web channel configuration in Journey Optimizer, targeting either a single page URL or multiple pages through a pages matching rule built with Domain and Path operators.

Intents:

  • Create a web channel configuration from Channels > General settings > Channel configurations
  • Target a single page by entering a Page URL
  • Target multiple pages by building a pages matching rule
  • Assign data usage labels to a configuration through Manage access (OLAC)
  • Associate consent policies to messages by selecting Marketing actions
  • Choose the right Domain and Path operators to match the intended URLs

Glossary:

  • Web channel configuration: A web property identified by a URL where content will be delivered; it can match a single page URL or multiple pages (product-specific)
  • Single page: Web settings option that applies changes to a single page by entering a Page URL (product-specific)
  • Pages matching rule: Web settings option that targets multiple URLs matching the same rule so the same content changes apply across multiple pages at once (product-specific)
  • Default authoring and preview URL: A URL entered for a pages matching rule so the pages generated or matched by the rule have a designated URL for content creation and preview (product-specific)
  • Marketing action: A selection that associates consent policies to messages using the configuration so customer preferences are respected (product-specific)
  • Wildcard matching: An operator allowing a wildcard (asterisk) match inside the Domain or Path string (product-specific)

Guardrails:

  • Configuration names must begin with a letter (A-Z) and can only contain alphanumeric characters plus underscore, dot, and hyphen.
  • You can add up to 10 rules when building a pages matching rule.
  • For the Domain “Wildcard matching” operator, the value must contain one and only one wildcard (asterisk).
  • A pages matching rule can be built when creating a web or code-based experience configuration.
  • The Or and Exclude operators can be used between the different rules.

Terminology:

  • Canonical name: Web channel configuration — Acronym: n/a — variants: web configuration, channel configuration
  • Synonyms: “Pages matching rule” = “rule that matches multiple pages”
  • Do not confuse: “Single page” (targets one Page URL) ≠ “Pages matching rule” (targets multiple URLs matching a rule)
  • Do not confuse: “Domain” operators ≠ “Path” operators (each section has its own available operators)

FAQ:

  • Q: How do I create a web channel configuration? — Go to Channels > General settings > Channel configurations, click Create channel configuration, enter a name, select the Web channel, choose Single page or Pages matching rule, then Submit.
  • Q: What characters are allowed in a configuration name? — It must begin with a letter (A-Z) and can only contain alphanumeric characters plus underscore, dot, and hyphen.
  • Q: How many rules can a pages matching rule contain? — You can add up to 10 rules, and use the Or or Exclude operators between them.
  • Q: How do I target more than one page? — Select Pages matching rule, define criteria for the Domain and Page fields, and enter a Default authoring and preview URL.
  • Q: When would I use the Exclude operator? — When one of the pages matching the defined rule should not be targeted.
recommendation-more-help
journey-optimizer-help