---
title: AJO Loyalty Configuration
slug: docs/ajo-loyalty-configuration
docTags: 
createdAt: 2026-08-19T06:19:19.330Z
---

# Introduction

This document provides guidance for configuring AJO Loyalty at the organization or sandbox level. It covers the minimum foundational requirements needed to set up the loyalty framework and begin creating and executing loyalty challenges within your environment.

:::hint{type="info"}
Prerequisite - You must have access to AJO loyalty tabs within your Org/sandbox.
:::

In order to demonstrate the steps for configuration we will use public project Luma configs in steps and you can carry out similar steps for your Loyalty configs.

## Configuration Steps

1.  Open the AJO and from left rail under Loyalty tab go to **Loyalty Configurations > Global Settings. **Define the configurations like **Namespace as email** and for reporting your datasets. For Luma we have used *Demo System Profile Dataset for Website* and *Demo System Event Dataset for Website* where our events are landing and mapped to loyalty schema. Save the changes.

::Image[]{src="https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/41f2_TqSQNvgqrxssvm3a_screenshot-2026-08-19-at-120350-pm.png" size="50" isUploading="false" position="center" width="747" height="676" darkWidth="747" darkHeight="676" showCaption="false"}

2.  Now go to next tab i.e. **Reward Providers **define the reward provider as per your need. For Luma we have used [request catcher ](https://requestcatcher.com/)(to demonstrate payload forward to external Rewards systems.) Also, we need to define **Reward Definition** as what payload to send to external system. Save the changes.

![](https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/cYD1tA51eEX4wZvb8M21__screenshot-2026-08-19-at-121213-pm.png)

**Reward Definition:** 

```json
{
"pointsRewarded": "100",
"ChallengeName": "Luma Gold Tier Challenge"
}
```

![](https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/8VX33qu_NjjhIeVTka36c_screenshot-2026-08-19-at-121547-pm.png)

3. Now go to **Event Definition** tab now define a event definition where your events will land(dataset and Schema) and mapped with Global Loyalty Schema. For Luma we have used *Website Event Schema* path and under transformer we have mapped our purchase events. *If you want to map your events with ****Global Loyalty Schema**** then go to this [link(JSONATA MAPPER)](https://loyalty-metadata-service-stage2.corp.ethos12-stage-va7.ethos.adobe.net/loyalty/apps) and paste your event payload and map it with ****Global Loyalty Schema ****and generate a valid transformer.*

![](https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/oJ3GIZNXmTFiv2-RlwGJA_screenshot-2026-08-19-at-122509-pm.png)

:::CodeblockTabs
JSONata

```json
{
  "timestamp": timestamp,
  "loyalty_identity": {
    "id": _demosystem4.identification.core.email
  },
  "item_list": [
    productListItems.{
      "item_set": [SKU],
      "quantity": quantity,
      "unit_price": priceTotal / quantity
    }
  ]
}
```
:::

4. Now go to **Product Inventory** tab and upload a file in the same format where product should be grouped by category as defined in screenshot. For Luma we have used all the products on Luma website and used categories to divide them and utilise at the task level.

![](https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/d-rkjncr0UDJuWKY6zIaD_screenshot-2026-08-19-at-122736-pm.png)

::File{src="https://api.archbee.com/api/presign/bAgVaanSi1tFmfc8PghaH/o0CillxyXCjB_NeMpma8a_luma3-products.csv" label="luma3-products.csv"}