Table of contents
Overview overview
Loyalty Challenges relies on Adobe Experience Platform for identity, profile attributes, experience events, and audiences. Use this page to learn which data to prepare, which datasets are involved, and how time-to-live (TTL) affects retention before you author challenges or use the Loyalty Challenges APIs.
Contact your Adobe administrator for Journey Optimizer program setup, or configure reward fulfillment and event mapping in the Loyalty admin menu. Learn how to configure loyalty challenges. For REST endpoints and authentication, see the Loyalty Challenges API reference.
Adobe Experience Platform data aep-data
Profile attributes profile-attributes
Challenge audiences, personalization, and reporting use profiles in the XDM Individual Profile class. Align the identity namespace you use for Loyalty Challenges with how members are identified in your profile data and with the namespace selected in Global settings in the Loyalty admin menu.
For standard loyalty attributes on the profile (points, tier, program, status, and related fields), use the Experience Platform Loyalty Details schema field group. That field group defines the loyalty object and its properties (for example points, tier, program, and status).
Experience events experience-events
Purchase, Spend, and Custom event tasks depend on experience events ingested into Adobe Experience Platform. For Custom event tasks, matching event definitions (identifier path, optional XDM schema ID, schema, and transformer) must be configured in the Loyalty admin menu before marketers can enter custom event values in the task builder. Learn how to configure event definitions
Ensure event payloads use the same identity namespace as your Loyalty Challenges configuration so progress can be attributed to the correct profile.
Audiences and reporting audiences-reporting
Marketers select Platform audiences when configuring challenge eligibility. Loyalty reporting dashboards use Adobe Customer Journey Analytics. Learn how to monitor loyalty challenge performance
Dataset time-to-live (TTL) dataset-ttl
Loyalty Challenges stores operational and reporting data in Adobe Experience Platform datasets (including event and personalization-related datasets created for your program). Dataset time-to-live (TTL) controls how long data is retained in the data lake and, when applicable, in the Profile store.
Journey Optimizer applies TTL guardrails to many system-generated datasets. Loyalty-related datasets follow the same Platform retention model for your sandbox.
➡️ Datasets Time-to-live (TTL) guardrails in Journey Optimizer