在此頁面上：建置符合必要結構的XDM體驗事件結構描述，以便將您的串流事件擷取到Adobe Experience Platform中，並用來觸發歷程。
Journey Optimizer事件是指透過串流擷取傳送至Adobe Experience Platform的XDM體驗事件。
因此，為Journey Optimizer設定事件的重要先決條件是，您熟悉Adobe Experience Platform的體驗資料模型（或XDM）、如何組成XDM體驗事件結構，以及如何將XDM格式的資料串流到Adobe Experience Platform。
Journey Optimizer個事件的結構描述需求 schema-requirements
為Journey Optimizer設定事件的第一步是確保您已定義代表該事件的XDM結構描述，以及已建立資料集以在Adobe Experience Platform上記錄該事件的執行個體。 嚴格來說，沒有必要為事件建立資料集，但將事件傳送至特定資料集可讓您維護使用者的事件歷史記錄，以供日後參考和分析，因此總是不錯的做法。 如果您還沒有適合事件的結構描述和資料集，這兩項工作都可以在Adobe Experience Platform網頁介面中完成。
將用於Journey Optimizer事件的任何XDM結構描述都應符合下列要求：
-
結構描述必須是XDM ExperienceEvent類別。
-
對於系統產生的事件，結構描述必須包括Orchestration eventID欄位群組。 Journey Optimizer使用此欄位來識別歷程中使用的事件。
-
宣告身分欄位，以識別事件中的個別設定檔。 如果未指定身分，則可使用身分對應。 不建議採用此做法。
-
如果您希望此資料可用於設定檔，請標籤設定檔的結構描述和資料集。 了解更多
-
您可以隨意加入資料欄位，以擷取您要與事件一併加入的任何其他內容資料，例如關於使用者的資訊、產生事件的裝置、位置或與事件相關的任何其他有意義的情況。
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 the requirements an XDM Experience Event schema must meet so that streamed events can be ingested into Adobe Experience Platform and used to trigger Journey Optimizer journeys.
Intents:
- Understand that Journey Optimizer events are XDM Experience Events sent to Adobe Experience Platform via Streaming Ingestion
- Build an XDM schema of the ExperienceEvent class for journey events
- Add the Orchestration eventID field group for system-generated events
- Declare an identity field to identify individual profiles in the event
- Mark the schema and dataset for profile so the data is available for profile
Glossary:
- XDM ExperienceEvent class: The class the schema must belong to for use with Journey Optimizer events (product-specific)
- Orchestration eventID field group: The field group that must be included for system-generated events, which Journey Optimizer uses to identify events used in journeys (product-specific)
- Identity map: The fallback that can be used to identify individual profiles when no identity field is specified, which is not recommended (product-specific)
- Streaming Ingestion: The mechanism by which XDM Experience Events are sent to Adobe Experience Platform (product-specific)
Guardrails:
- The schema must be of the XDM ExperienceEvent class.
- For system-generated events, the schema must include the Orchestration eventID field group.
- An identity field should be declared to identify individual profiles; if no identity is specified, an identity map can be used, which is not recommended.
- To make the data available for profile, mark the schema and dataset for profile.
- Starting July 8, 2025, new customer organizations cannot create expressions using experience event attributes in journey conditions.
- Starting April 1, 2026, organizations that have not accessed experience events via journey expressions in the last 90 days will no longer have access to this capability; accessing context from the starting event of a journey is not impacted.
Terminology:
- Canonical name: XDM ExperienceEvent schema — Acronym: XDM — variants: XDM Experience Event schema, ExperienceEvent class schema
- Do not confuse: “identity field” (declared field for identifying individual profiles, recommended) ≠ “identity map” (fallback used when no identity is specified, not recommended)
FAQ:
- Q: What class must the schema use? — The schema must be of the XDM ExperienceEvent class.
- Q: What is required for system-generated events? — The schema must include the Orchestration eventID field group, which Journey Optimizer uses to identify events used in journeys.
- Q: Is a dataset required for the events? — Having a dataset is not strictly necessary, but sending events to a specific dataset lets you maintain users’ event history for future reference and analysis.
- Q: What happens if I do not declare an identity field? — An identity map can be used instead, but this is not recommended.
- Q: Are experience event attributes in journey conditions still available? — Starting July 8, 2025, new customer organizations cannot create such expressions, and starting April 1, 2026, organizations that have not accessed them via journey expressions in the last 90 days lose access; accessing context from the starting event is not impacted.