在此页面上：配置数据源并定义字段组，以便您只能检索历程所需的特定数据。
要配置数据源，请执行以下步骤：
定义字段组 define-field-groups
字段组是可从数据源检索并在历程中使用的一组字段。
对于每个数据源，您可以定义多个字段组。
例如，您可以创建一个字段组，其中包含电话号码、电子邮件、名字和个人资料的地址。 然后，您便能够在历程中使用此数据来创建条件。 例如，您可以决定仅在客户安装了移动应用程序时才发送推送通知。 如果为空，您可以发送电子邮件。
即使自动添加了默认名称，我们仍建议您为字段组提供一个名称。 事实上，字段组名称将对Journey Optimizer中的其他用户可见。 为字段组指定相关名称是一种最佳实践。
在历程中使用数据源字段时，系统将检索为该字段组定义的所有字段。 因此，最佳实践是仅选择历程所需的字段。 这将减少历程中的请求延迟，从而提高性能。 请注意，您可以稍后在字段组中轻松添加更多字段。
使用字段组的旅程数显示在 用于 字段中。 您可以单击 查看历程 按钮以显示使用此字段组的历程列表。
字段组生命周期 field-group-lifecycle
您可以从未在任何草稿或实时历程中使用的字段组中添加或删除字段。
如果字段组用于一个或多个草稿或实时历程，则可以从所选架构增量添加新字段，但无法取消选择/删除/修改已选择的字段。 如果修改了草稿或实时历程已在使用的架构的现有字段（例如，更改字段的数据类型），则不允许更新字段组。 这将避免中断历程
要从一个或多个历程中使用的字段组中删除字段，请执行以下步骤。 让我们举一个名为“字段组A”的字段组为例。
- 在字段组列表中，将光标置于“字段组A”上，然后单击右侧的 复制 图标。 例如，将复制的字段组命名为“字段组B”。
- 在“字段组B”中，删除您不再需要的字段。
- 在“字段组A”中，检查在何处使用此字段组。 此信息显示在 用于 字段中。
- 打开所有使用“字段组A”的历程。
- 创建每个历程的新版本。 使用“字段组A”编辑所有活动并选择“字段组B”。
- 停止使用“字段组A”的旧版本历程。 然后，您应该没有使用“字段组A”的历程。
- 删除“字段组A”，因为它已不再使用。
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 configure a data source from the Configurations menu and how to define field groups so your journeys retrieve only the specific data they need.
Intents:
- Configure a data source from the Administration Configurations menu
- Define one or several field groups for a data source
- Name field groups and select only the fields needed to reduce request latency
- Check how many journeys use a field group with the Used in field and View journeys button
- Add fields to, or remove fields from, a field group according to its lifecycle rules
Glossary:
- Field group: A set of fields that you can retrieve from a data source and use in a journey (product-specific)
- Used in: The field that displays the number of journeys using a field group, with a View journeys button to list them (product-specific)
Guardrails:
- The data source configuration is always performed by a technical user.
- When a data source field is used in a journey, the system retrieves all fields defined for that field group; selecting only the fields you need reduces request latency and increases performance.
- If a field group has no field, it is not displayed in the expression editor.
- You can add or remove fields from a field group only if it is not used in any draft or live journey.
- If a field group is used in one or more draft or live journeys, you can incrementally add new fields from the selected schema, but cannot deselect, remove, or modify fields that have already been selected.
- Updates to a field group are not permitted if existing fields of a schema already in use by draft or live journeys are modified, for example changing the data type of a field.
Terminology:
- Canonical name: field group — Acronym: n/a — variants: field groups
- Do not confuse: “add fields to the built-in data source” ≠ “create a new external data source”
FAQ:
- Q: Where do I configure a data source? — In the Administration menu section, select Configurations, then in the Data Sources section click Manage to display the list of data sources.
- Q: Why should I select only the fields I need in a field group? — When a field is used in a journey, the system retrieves all fields defined for that field group, so selecting only the fields you need reduces request latency and increases performance.
- Q: Why is my field group not showing in the expression editor? — If a field group has no field, it is not displayed in the expression editor.
- Q: Can I modify fields already used by a draft or live journey? — No, if a field group is used in one or more draft or live journeys you can incrementally add new fields but cannot deselect, remove, or modify fields already selected.
- Q: How do I remove a field from a field group used in journeys? — Duplicate the field group, remove the unwanted fields in the duplicate, update each journey to use the duplicate, stop the old journey versions, and then remove the original field group once it is no longer used.