DocumentationJourney OptimizerJourney Optimizer Guide

Configure Content cards content-card-configuration

Last update: September 13, 2026

CREATED FOR:

  • Experienced
  • Admin

On this page: Create a Content card channel configuration and define its surface so you can deliver content cards to the right web or app location.

style
shade-box

What is a configuration? surface-definition

A content card experience configuration is any entity designed for user or system interaction, which is uniquely identified by an URI.

In other words, a surface can be seen as a container at any level of hierarchy with an entity (touchpoint) that exists.

  • It can be a web page, a mobile app, a desktop app, a specific content location within a larger entity (for example a div), or a non-standard display pattern (for example, a kiosk or a desktop app banner).

  • It can also extend to specific pieces of content containers for non-display or abstracted-display purposes (for example, JSON blobs delivered to services).

  • It can also be a wildcard surface that matches a variety of client-surface definitions (for example, a hero image location on every page of your website could translate in a surface URI like: web://mydomain.com/*#hero_image).

Basically a surface URI is composed of multiple sections:

  1. Type: web, mobileapp, atm, kiosk, tvcd, service, etc.
  2. Property: page URL or app bundle
  3. Container: location on the page/app activity

The tables below list some surface URI definition examples for various devices.

Web and mobile

Type
URI
Description
Web
web://domain.com/path/page.html#element
Represents an individual element within a specific page of a specific domain, where an element can be a label like in the following examples: hero_banner, top_nav, menu, footer, etc.
iOS app
mobileapp://com.vendor.bundle/activity#element
Represents a specific element within a native app activity, such as a button or other view element.
Android app
mobileapp://com.vendor.bundle/#element
Represents a specific element within a native app.

Other device types

Type
URI
Description
Desktop
desktop://com.vendor.bundle/#element
Represents a specific element within an application, such as a button, menu, hero banner, etc.
TV app
tvcd://com.vendor.bundle/#element
Represents a specific element within a smart TV or TV connected device app - bundle ID.
Service
service://servicename/#element
Represents a server-side process or other manual entity.
Kiosk
kiosk://location/screen#element
Example of potential additional surface types that can be added easily.
ATM
atm://location/screen#element
Example of potential additional surface types that can be added easily.

Wildcard surfaces

Type
URI
Description
Wildcard web
wildcard:web://domain.com/*#element
Wildcard surface - represents an individual element in each of the pages under a specific domain.
Wildcard web
wildcard:web://*domain.com/*#element
Wildcard surface - represents an individual element in each of the pages under all domains that end with “domain.com”.

Create a content card configuration create-config

  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 Content card 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. Select the platform for which the content card experience will be applied.

  7. For Web:

    • Specify a Page URL to apply changes to a single page exclusively.

    • Or create a Pages matching rule to target multiple URLs that match the specified rule. For instance, this could be used to apply changes universally across a website, such as updating a hero banner across all pages or adding a top image to display on every product page. Learn more

  8. For iOS and Android:

    • Enter or select your App id, Location or path inside the app and Preview URL.

  9. Submit your changes.

You can now select your configuration when creating your Content card experience.

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 what a content card experience configuration and its surface URI are, and how to create a content card channel configuration in Journey Optimizer.

Intents:

  • Understand what a content card experience configuration and a surface are
  • Learn how a surface URI is composed from type, property, and container
  • Reference surface URI examples for web, mobile, other device types, and wildcard surfaces
  • Create a content card channel configuration from the Channel configurations menu
  • Associate marketing actions and platform settings with the configuration
  • Define web targeting with a page URL or a pages matching rule, or app targeting for iOS and Android

Glossary:

  • Content card experience configuration: Any entity designed for user or system interaction, uniquely identified by a URI (product-specific)
  • Surface: A container at any level of hierarchy with an entity (touchpoint) that exists, such as a web page, mobile app, desktop app, or a specific content location (product-specific)
  • Surface URI: The unique identifier of a surface, composed of a type, a property, and a container (product-specific)
  • Wildcard surface: A surface that matches a variety of client-surface definitions, for example web://mydomain.com/*#hero_image (product-specific)
  • Marketing action: A selection that associates consent policies with the messages using the configuration, so customer preferences are respected (product-specific)
  • Pages matching rule: A web targeting option that targets multiple URLs matching a specified rule (product-specific)

Guardrails:

  • A content card experience configuration is uniquely identified by a URI.
  • Configuration names must begin with a letter (A-Z) and can only contain alpha-numeric characters, plus the underscore, dot, and hyphen characters.
  • For Web, specify a Page URL to apply changes to a single page exclusively, or create a Pages matching rule to target multiple URLs that match the rule.
  • For iOS and Android, enter or select the App id, Location or path inside the app, and Preview URL.
  • All consent policies associated with the selected marketing action are leveraged to respect customer preferences.

Terminology:

  • Canonical name: Content card channel configuration — Acronym: URI (surface URI) — variants: content card experience configuration, content card configuration
  • Synonyms: “surface” = “content card experience configuration”
  • Do not confuse: “Page URL” (targets a single page exclusively) ≠ “Pages matching rule” (targets multiple URLs that match a rule)
  • Do not confuse: “Type” (web, mobileapp, atm, kiosk, tvcd, service) ≠ “Property” (page URL or app bundle) ≠ “Container” (location on the page or app activity)

FAQ:

  • Q: What is a content card experience configuration? — It is any entity designed for user or system interaction, uniquely identified by a URI, and can be seen as a container (surface) holding a touchpoint entity.
  • Q: What are the parts of a surface URI? — A surface URI is composed of a type (web, mobileapp, atm, kiosk, tvcd, service, and so on), a property (page URL or app bundle), and a container (location on the page or app activity).
  • Q: What characters are allowed in a configuration name? — Names must begin with a letter (A-Z) and can only contain alpha-numeric characters, plus the underscore, dot, and hyphen characters.
  • Q: How do I target web pages with the configuration? — Specify a Page URL to apply changes to a single page exclusively, or create a Pages matching rule to target multiple URLs that match the specified rule.
  • Q: Where do I create a content card configuration? — Access Channels > General settings > Channel configurations, click Create channel configuration, select the Content card channel, then configure and submit.
recommendation-more-help
journey-optimizer-help