The purpose of this document is to outline the necessary steps to walk through a sample Demo of an AJO Loyalty Challenge in AJO.

NOTE: The "Total Time" for completion of creating a Task, creating a Challenge and testing the Challenge takes approximately 1.5 hours for completion in an HOL setting. If you want to do this ONLY as a Demo, you should budget about 20-30 minutes. Keep these time frames in mind as you work with your Adobe Team and client requests.

Before challenges can be authored, an administrator configures the program foundations: reward providers, event definitions that map customer actions to task completions, product inventory, and exclusion lists.

Marketers create challenges by selecting a type (Standard, Streak, Sequential, or Bring your own data), configuring settings (audience, schedule, rules), and defining tasks and rewards. They can optionally surface the challenge on member-facing interfaces using a content card or code-based experience, and set up channel notifications for key moments across the challenge lifecycle. Once configured, they publish the challenge, generate the auto-built journey, and publish it to make the challenge live.

The steps / process for creating a Journey which utilizes the AJO Loyalty Challenge are relatively the same as previous design documentation has provided. The steps include:

One distinction for the AJO Loyalty Journey will be the inclusion of "Loyalty Events". Note that these are different from standard AJO Events that are created through Configurations -> Events. These are two separate event types. The distinction is that the Standard Event utilizes the Standard Event Schema, whereas Loyalty Events utilize the Loyalty Events Schema.

Use Loyalty Challenges reporting to see how your challenges are performing. Check who is signing up, who is completing challenges, and how much revenue your program is generating — all in one place. Data comes from Adobe Customer Journey Analytics.

To open the reporting dashboards, go to Loyalty Challenges in Journey Optimizer and select Performance in the left navigation.

The reporting interface has two tabs: