Configure Content cards

Last update: 2025-04-07

What is a configuration?

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:

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

Access the Channels > Branding > 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 Content card 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
Select the platform for which the content card experience will be applied.
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
For iOS and Android:
- Enter or select your App id, Location or path inside the app and Preview URL.
Submit your changes.