Adobe Experience Platform 資料來源 adobe-experience-platform-data-source

在此頁面上:​在內建的Adobe Experience Platform資料來源上設定欄位群組,以便您在歷程中擷取並使用即時客戶設定檔資料。

Adobe Experience Platform 資料來源會定義和 Adobe 即時客戶設定檔的連線。 此資料來源是內建和預先設定的,並無法刪除。 此資料來源旨在擷取及使用即時客戶個人檔案服務的資料(例如,檢查進入歷程的人員是否為女性)。 如需Adobe即時客戶個人檔案的詳細資訊,請參閱Adobe Experience Platform檔案

若要允許連線到即時客戶個人檔案服務,我們必須使用金鑰來識別人員,並使用名稱空間將金鑰內容化。 因此,如果您的歷程以包含索引鍵和名稱空間的事件開始,您只能使用此資料來源。 了解更多

您可以編輯名為「ProfileFieldGroup」的預先設定欄位群組、新增欄位群組,以及移除未用於任何草稿或即時歷程的欄位群組。 了解更多

CAUTION
不支援在歷程運算式/條件中使用體驗事件。 如果您的使用案例需要使用體驗事件,請考慮替代方法。 了解更多

將欄位群組新增至內建資料來源的主要步驟詳述如下:

  1. 從資料來源清單中,選取內建的​ Adobe Experience Platform ​資料來源。

    這會開啟畫面右側的資料來源設定窗格。

  2. 選取​ 新增欄位群組 ​以定義要擷取的新欄位系列

  3. 從​ 結構描述 ​下拉式清單中選取結構描述。 結構描述建立是在Adobe Experience Platform中執行,而非在Adobe Journey Optimizer中執行。

    note
    NOTE
    Journey Optimizer Data Source設定僅支援XDM個別設定檔結構描述。 如需詳細資訊,請參閱XDM個別設定檔類別
  4. 選取要使用的欄位,並儲存變更。

TIP
將滑鼠懸停在欄位群組的名稱上,可在右側顯示兩個圖示。 使用這些來​ 複製 ​或​ 刪除 ​欄位群組。 請注意,刪除​圖示只有在任何​即時草稿​或​ 已完成 ​歷程中未使用欄位群組時才可用。 請參考​ 用於 ​欄位以檢查情況是否如此。
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 add field groups to the built-in, pre-configured Adobe Experience Platform data source so you can retrieve and use Real-time Customer Profile data in your journeys.

Intents:

  • Add field groups to the built-in Adobe Experience Platform data source
  • Select an XDM Individual Profile-based schema and choose the fields to retrieve
  • Edit the pre-configured ProfileFieldGroup or create new field groups
  • Remove field groups that are not used in any journey
  • Understand the key and namespace requirement for using this data source

Glossary:

  • Adobe Experience Platform data source: The built-in, pre-configured data source that defines the connection to Adobe Real-time Customer Profile and cannot be deleted (product-specific)
  • ProfileFieldGroup: The pre-configured field group on the Adobe Experience Platform data source that you can edit (product-specific)
  • Key: The identifier used to identify a person for the connection to the Real-time Customer Profile Service (product-specific)
  • Namespace: The value that contextualizes the key (product-specific)

Guardrails:

  • This data source is built-in and pre-configured, and cannot be deleted.
  • You can only use this data source if your journeys start with an event containing a key and a namespace.
  • Only XDM Individual Profile-based schemas are supported in the Journey Optimizer Data Source configuration.
  • Using experience events in journey expressions/conditions is not supported.
  • Schema creation is performed in Adobe Experience Platform, not in Adobe Journey Optimizer.
  • The Delete icon for a field group is only available if the field group is not used in any Live, Draft or Finished journey; check the Used in field.

Terminology:

  • Canonical name: Adobe Experience Platform data source — Acronym: n/a — variants: built-in data source, pre-configured data source
  • Synonyms: “Adobe Experience Platform data source” = “built-in data source”
  • Do not confuse: “schema” (created in Adobe Experience Platform) ≠ “field group” (defined in Journey Optimizer to select which fields to retrieve)

FAQ:

  • Q: Can this data source be deleted? — No, it is built-in and pre-configured and cannot be deleted.
  • Q: What must my journey include to use this data source? — Your journey must start with an event containing a key and a namespace.
  • Q: Which schemas can I select? — Only XDM Individual Profile-based schemas are supported in the Journey Optimizer Data Source configuration.
  • Q: When can I delete a field group? — The Delete icon is only available if the field group is not used in any Live, Draft or Finished journey; the Used in field shows where it is used.
  • Q: Can I use experience events in journey expressions or conditions with this data source? — No, using experience events in journey expressions/conditions is not supported; consider alternative methods for that use case.
recommendation-more-help
journey-optimizer-help