在此页面上：创建内容卡渠道配置并定义其表面，以便您可以将内容卡交付到正确的Web或应用程序位置。
什么是配置？ surface-definition
内容卡体验配置是为用户或系统交互而设计的任何实体，它由 URI 唯一标识。
换句话说，可以将表面视为具有实体（接触点）的任何层级层次结构中的容器。
-
它可以是网页、移动设备应用程序、桌面应用程序、大型实体中的特定内容位置（例如
div）或非标准显示模式（例如，自助服务亭或桌面应用程序横幅）。 -
还可以扩展到用于非显示或抽象显示目的的特定内容容器（例如，传递给服务的 JSON Blob）。
-
它还可以是匹配各种客户端表面定义的通配符表面（例如，网站每个页面上的主图像位置可以在表面 URI 中进行转译，例如：web://mydomain.com/*#hero_image）。
表面 URI 基本上由多个部分组成：
- 类型：web、mobileapp、atm、kiosk、tvcd、service 等。
- 属性：页面 URL 或应用程序捆绑包
- 容器：页面/应用程序活动上的位置
下表列出了各种设备的一些表面 URI 定义示例。
Web 和移动
web://domain.com/path/page.html#elementmobileapp://com.vendor.bundle/activity#elementmobileapp://com.vendor.bundle/#element其他设备类型
desktop://com.vendor.bundle/#elementtvcd://com.vendor.bundle/#elementservice://servicename/#elementkiosk://location/screen#elementatm://location/screen#element通配符表面
wildcard:web://domain.com/*#elementwildcard:web://*domain.com/*#element创建内容卡配置 create-config
-
访问渠道 > 常规设置 > 渠道配置菜单，然后单击创建渠道配置。
-
输入配置的名称和说明（可选）。
note NOTE 名称必须以字母(A-Z)开头。 它只能包含字母数字字符。 您还可以使用下划线 _、点.和连字符-符号。 -
要为配置分配自定义或核心数据使用标签，您可以选择管理访问权限。 了解有关对象级访问控制(OLAC)的更多信息。
-
选择 内容卡 渠道。
-
选择 营销操作 以使用此配置将同意策略关联到消息。 所有与营销活动相关的同意政策均可利用，以尊重客户的偏好。 了解详情
-
选择要应用内容卡体验的平台。
-
对于Web：
-
指定 页面URL 以独占地应用对单个页面的更改。
-
或者，创建与规则 匹配的 页面，以定位多个与指定规则匹配的URL。 例如，这可用于在网站中通用应用更改，例如在所有页面中更新主页横幅，或添加要在每个产品页面上显示的顶部图像。 了解详情
-
-
对于iOS和Android：
- 输入或选择您的应用程序ID、应用程序内的位置或路径和预览URL。
-
提交更改。
现在，您可以在创建内容卡体验时选择配置。
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.