忠诚度数据和数据集 loyalty-data-and-datasets

在此页面上:​了解哪些Adobe Experience Platform身份、用户档案、事件、受众和数据集支持忠诚度挑战,以及数据集生存时间如何影响数据保留。

概述 overview

忠诚度挑战依赖于Adobe Experience Platform的身份标识、配置文件属性、体验事件和受众。 使用此页面可了解要准备哪些数据、涉及哪些数据集以及​ 生存时间(TTL) ​在您创作挑战或使用忠诚度挑战API之前对保留率有何影响。

请联系Adobe管理员以设置Journey Optimizer,或在​ 忠诚度配置 ​菜单中配置奖励履行和事件映射。 了解如何配置忠诚度挑战。 有关REST端点和身份验证,请参阅忠诚度挑战元数据API引用和忠诚度挑战状态API引用。

通过源的忠诚度连接器 loyalty-connectors-sources

如果您的忠诚度数据在外部奖励平台中进行管理,则您可以使用​ 源 ​连接器将该数据摄取到Adobe Experience Platform,然后将其用于忠诚度挑战中。

Journey Optimizer文档中列出的忠诚度和奖励连接器包括:

  • Talon.One
  • 毛细管
  • 小作品
  • 熔岩

有关连接器入门和端到端设置,请参阅源连接器入门和Experience Platform源目录。

Adobe Experience Platform数据 aep-data

轮廓属性 profile-attributes

在​ XDM Individual Profile ​类中挑战受众、个性化和报告使用配置文件。 将您用于忠诚度挑战的标识命名空间与您在个人资料数据中的成员标识方式以及在​ 忠诚度配置 ​菜单的​ 全局设置 ​中选择的命名空间保持一致。

对于配置文件上的标准忠诚度属性(积分、层、计划、状态和相关字段),请使用Experience Platform 忠诚度详细信息​架构字段组。 该字段组定义loyalty对象及其属性(例如points、tier、program和status)。

➡️ 忠诚度详细信息架构字段组

➡️ Adobe Journey Optimizer架构引用

体验事件 experience-events

购买、支出​和​ 自定义事件 ​任务依赖于摄取到Adobe Experience Platform中的体验事件。 对于​ 自定义事件 ​任务,必须在​ 忠诚度配置 ​菜单中配置匹配的事件映射(事件名称、体验事件架构和字段映射),然后营销人员才能在任务生成器中输入自定义事件值。 了解如何配置事件映射

确保事件有效负载使用与“忠诚度挑战”配置相同的身份命名空间,以便将进度归因于正确的配置文件。

受众和报表 audiences-reporting

营销人员在配置挑战资格时选择Platform 受众。 忠诚度绩效仪表板使用Adobe Customer Journey Analytics。 了解忠诚度绩效

数据集生存时间(TTL) dataset-ttl

忠诚度挑战将操作和报表数据存储在Adobe Experience Platform数据集中(包括为您的项目创建的事件和个性化相关数据集)。 数据集​ 生存时间(TTL) ​控制数据在数据湖中保留多长时间,如果适用,在配置文件存储中保留多长时间。

Journey Optimizer将TTL护栏应用于许多系统生成的数据集。 与忠诚度相关的数据集遵循与沙盒相同的平台保留模型。

在Journey Optimizer中➡️ 数据集生存时间(TTL)护栏

NOTE
组织级别的忠诚度配置可以包括通过忠诚度元数据服务管理的存档和保留设置(例如存档持续时间)。 如果需要调整组织的维系率,请与Adobe管理员协调。
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 lists the Adobe Experience Platform identities, profile attributes, experience events, audiences, and datasets that Loyalty Challenges requires, and explains how dataset time-to-live affects data retention.

Intents:

  • Identify which Adobe Experience Platform profile attributes, experience events, audiences, and datasets support Loyalty Challenges.
  • Align the identity namespace used for Loyalty Challenges with how members are identified in profile data.
  • Configure event mappings so marketers can enter custom event values in the task builder.
  • Ingest external loyalty data into Adobe Experience Platform using Sources connectors.
  • Understand how dataset time-to-live affects retention of loyalty-related data.

Glossary:

  • Loyalty configurations: the menu where reward fulfillment and event mapping are configured (product-specific)
  • Global settings: the area within the Loyalty configurations menu where the identity namespace is selected (product-specific)
  • Loyalty Details: the Experience Platform schema field group that defines the loyalty object and its properties (for example points, tier, program, and status) (product-specific)
  • Purchase, Spend, Custom event tasks: task types that depend on experience events ingested into Adobe Experience Platform (product-specific)
  • Dataset time-to-live (TTL): controls how long data is retained in the data lake and, when applicable, in the Profile store (product-specific)

Guardrails:

  • Event payloads must use the same identity namespace as the Loyalty Challenges configuration so progress can be attributed to the correct profile.

Prerequisites and permissions:

  • Matching event mappings (event name, Experience event schema, and field mappings) must be configured in the Loyalty configurations menu before marketers can enter custom event values in the task builder for Custom event tasks.

Terminology:

  • Acronym: TTL — Time-to-live
  • Do not confuse: “Loyalty configurations” (menu for reward fulfillment and event mapping) ≠ “Global settings” (sub-area for identity namespace selection)

FAQ:

  • Q: Which Experience Platform class do challenge audiences, personalization, and reporting use? — Profiles in the XDM Individual Profile class.
  • Q: What schema field group holds standard loyalty attributes on the profile? — The Loyalty Details field group, which defines the loyalty object and properties such as points, tier, program, and status.
  • Q: What must be configured before marketers can enter custom event values for Custom event tasks? — Matching event mappings (event name, Experience event schema, and field mappings) in the Loyalty configurations menu.
  • Q: How can external loyalty or rewards data be used in Loyalty Challenges? — Ingest it into Adobe Experience Platform using Sources connectors.
  • Q: How does dataset TTL affect Loyalty Challenges? — Dataset time-to-live controls how long operational and reporting data is retained in the data lake and, when applicable, in the Profile store. Journey Optimizer applies TTL guardrails to many system-generated datasets, and loyalty-related datasets follow the same Platform retention model for your sandbox.

Related pages:

  • For configuring loyalty challenges and event mappings: Learn how to configure loyalty challenges (loyalty-challenges/loyalty-admin.md)
  • For connector onboarding and end-to-end setup: Get started with sources connectors (start/get-started-sources.md)
  • For selecting audiences when configuring challenge eligibility: audiences (audience/about-audiences.md)
  • For exploring loyalty performance dashboards: Explore Loyalty performance (loyalty-challenges/loyalty-performance.md)
  • For dataset retention guardrails: Datasets Time-to-live (TTL) guardrails in Journey Optimizer (data/datasets-ttl.md)

Personas:

  • admin: Can coordinate with the Adobe administrator to adjust organization-level archive and retention settings managed through the Loyalty metadata service. The page states that dataset time-to-live controls how long data is retained in the data lake and, when applicable, in the Profile store. Where: “Dataset time-to-live (TTL)”.
  • developer: Can use the Loyalty Details schema field group, which defines the loyalty object and properties such as points, tier, program, and status. Can configure event mappings (event name, Experience event schema, and field mappings) in the Loyalty configurations menu for Custom event tasks, before marketers enter custom event values in the task builder. The page states that event payloads must use the same identity namespace as the Loyalty Challenges configuration so progress can be attributed to the correct profile. Where: “Experience events”.

Onboarding:

  • Level: Intermediate
  • First minimal step: Configure reward fulfillment and event mapping in the Loyalty configurations menu.
  • Success check: Marketers can enter custom event values in the task builder.
recommendation-more-help
journey-optimizer-help