在此頁面上：建立內容卡頻道設定並定義其介面，讓您可以將內容卡傳送至正確的網頁或應用程式位置。
什麼是設定？ surface-definition
內容卡體驗組態是任何專為使用者或系統互動而設計的實體，可由 URI 唯一識別。
換言之，若有任何階層層級具有實體（接觸點）存在，則可將表面視為容器。
-
可以是網頁、行動應用程式、案頭應用程式、大型實體中的特定內容位置（例如
div），或非標準顯示模式（例如，資訊站或案頭應用程式橫幅）。 -
其也可以延伸至內容容器的特定片段，用於非顯示或抽象顯示目的 (例如，傳遞至服務的 JSON Blob)。
-
其也可以是符合各種用戶端介面定義的萬用字元表面 (例如，網站每個頁面上的主圖影像位置可翻譯為表面URI，例如：web://mydomain.com/*#hero_image)。
基本上，表面 URI 由多個區段組成：
- 類型：網頁、行動應用程式、ATM、資訊站、tvcd、服務等
- 屬性：頁面 URL 或應用程式套裝
- 容器：頁面/應用程式活動上的位置
下表列出各種裝置的一些表面 URI 定義範例。
網頁與行動裝置
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.