在此页面上：构建符合所需结构的XDM Experience Event架构，以便将您的流式事件摄取到Adobe Experience Platform中并用于触发历程。
Journey Optimizer事件是通过流式摄取发送到Adobe Experience Platform的XDM Experience事件。
因此，为Journey Optimizer设置事件的一项重要先决条件是，您熟悉Adobe Experience Platform的体验数据模型（或XDM）、如何构建XDM体验事件架构以及如何将XDM格式的数据流式传输到Adobe Experience Platform。
Journey Optimizer事件的架构要求 schema-requirements
为Journey Optimizer设置事件的第一步是确保您定义了用于表示该事件的XDM架构，并创建了数据集以在Adobe Experience Platform上记录该事件的实例。 严格来说，为事件创建数据集并不是必需的，但将事件发送到特定数据集将允许您维护用户的事件历史记录，以供将来参考和分析，因此始终是一个不错的主意。 如果您还没有适合事件的架构和数据集，则可以在Adobe Experience Platform Web界面中完成这两项任务。
将用于Journey Optimizer事件的任何XDM架构都应满足以下要求：
-
架构必须为XDM ExperienceEvent类。
-
对于系统生成的事件，架构必须包括编排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.