在此页面上：了解什么是数据源以及如何选择正确的数据访问策略，以便在历程中引入附加数据，了解条件、个性化和时间安排。
数据源配置允许您定义与系统的连接，以检索将在您的历程中使用的其他信息，例如：
➡️ 通过观看视频了解此功能
如果您的历程只利用来自事件有效负载的本地数据，则不需要此配置。 例如，如果您的历程由一个事件组成，后跟一个只使用事件数据的渠道操作活动，则无需配置数据源。
数据源有两种类型：
对于每个数据源，您定义要使用字段组检索的信息。 字段组是可从数据源检索的字段集。 请参阅此页。
选择您的数据访问策略 data-access-strategy
在配置数据源之前，请考虑哪种方法最适合您的用例。 提供了三种选项，每种选项在持久性、配置文件扩充和可重用性方面都有不同的取舍。 有关这些选项的详细讨论，请参阅Journey Optimizer中高级历程的最佳实践。
选项1 — 通过自定义操作（无数据湖）访问外部数据
在旅程运行时直接连接到外部API，而无需将数据保留在Experience Platform数据湖中。 最适合以下情况：
- 数据仅在历程上下文中有用，而在其他位置则不需要它。
- 可通过返回所需属性的API端点访问外部系统。
- 数据是否仅在历程上下文中有用，而不在其他地方需要？ 如果受众或其他渠道还需要数据，请考虑选项2或3。
- 是否可以通过返回所需属性的API端点访问外部系统？ 如果不能，您将需要先将数据摄取到数据湖。
选项2 — 数据湖中的数据集，未为配置文件启用
将数据摄取到数据集中，以根据上下文事件数据触发历程并对历程进行个性化，而不会影响实时客户个人资料。 最适合以下情况：
- 记录中包含一个标识字段，用于访问已存储在Experience Platform中的用户档案。
- 在Journey Optimizer之外创建受众或拼合身份时不需要数据。
- 记录是否包含可用于访问Experience Platform中已存储的用户档案的身份字段？ 否则，历程将无法访问并交付到用户档案。
- 在Journey Optimizer之外创建受众或拼合身份时是否不需要数据？ 如果是，请改用选项3。
选项3 — 数据湖中启用了配置文件的数据集
将数据摄取到启用了配置文件的数据集中以创建受众、丰富身份图，并在多个历程和RT-CDP目标中利用数据。 最适合以下情况：
- 这些数据可用于Journey Optimizer以外的渠道中使用的受众定义。
- 数据包含多个身份，这些身份有助于创建更丰富的拼接配置文件片段。
有关如何配置 Adobe Experience Platform 数据源和外部数据源以及如何在历程中查找和使用数据的更多信息，请观看此教程视频。
操作方法视频 video
了解什么是数据源以及如何配置 Experience Platform 和外部数据源。
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 data sources are in Journey Optimizer, the two types available (the built-in Adobe Experience Platform data source and external data sources), and how to choose between three data access strategies before configuring one.
Intents:
- Understand what a data source is and when a data source configuration is needed
- Distinguish the pre-configured Adobe Experience Platform data source from external data sources
- Choose a data access strategy among the three available options
- Understand what field groups are used for on a data source
- Decide whether to access external data via custom actions, ingest into a dataset, or use a profile-enabled dataset
Glossary:
- Data source: A configuration that defines a connection to a system to retrieve additional information used in journeys for condition definition, parameter and personalization data in actions, custom wait definition, and time zone definition (product-specific)
- Pre-configured Adobe Experience Platform data source: The built-in data source that defines the connection to the Real-time Customer Profile Service (product-specific)
- External data source: A data source you create to define a connection to external systems (product-specific)
- Field group: A set of fields that can be retrieved from a data source (product-specific)
Guardrails:
- The data source configuration is always performed by a technical user.
- A data source configuration is not required if your journeys only leverage local data coming from an event payload.
- Schema relationships are not supported for data sources.
- Because responses are now supported, you should use custom actions instead of data sources for external data source use-cases.
- Before enabling a dataset for Profile (Option 3), assess data synchronization, Profile guardrails, identity integrity, and Data Lake utilization.
Terminology:
- Canonical name: data source — Acronym: n/a — variants: data source configuration
- Synonyms: “pre-configured Adobe Experience Platform data source” = “built-in data source”
- Do not confuse: “Adobe Experience Platform data source” (pre-configured, built-in) ≠ “external data source” (one you create)
- Do not confuse: “Option 2 — Dataset in Data Lake, not enabled for Profile” (persisted, not contributing to Profile) ≠ “Option 3 — Profile-enabled dataset in Data Lake” (persisted and enabled for Profile)
FAQ:
- Q: When is a data source configuration required? — It is not required if your journeys only use local data coming from an event payload; it is needed when you want to retrieve additional information for conditions, personalization, custom wait, or time zone.
- Q: What are the two types of data sources? — The pre-configured Adobe Experience Platform data source (built-in) and external data sources that you create.
- Q: How many external data sources can I create? — You can create as many external data sources as you need.
- Q: Which data access strategy should I choose? — Option 1 accesses external data via custom actions without persisting in the Data Lake, Option 2 ingests into a dataset not enabled for Profile, and Option 3 uses a profile-enabled dataset; choose based on persistence, profile enrichment, and reusability needs.
- Q: Are schema relationships supported for data sources? — No, schema relationships are not supported for data sources.