> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/playbook/introduction/common-concepts.md).

# Common concepts

A short definition of each Open Loyalty module the Playbook refers to, with a link to its full description in the User Guide.

The Playbook's sample setups are built from Open Loyalty modules. This page says what each module is, grouped the way the [User Guide](https://help.openloyalty.io/) groups them. Follow the links for how each one works and how to configure it.

{% hint style="info" %}
A program doesn't need every module. Each sample setup lists the modules it uses.
{% endhint %}

***

## 📊 Getting started

**Dashboard** – an overview of program performance: registered and active members, revenue, average spending and transaction values.\
👉 [Dashboard](https://help.openloyalty.io/dashboard)

**Global Management** – compares metrics such as new members, active members and transactions across all your tenants.\
👉 [Global Management](https://help.openloyalty.io/global-management)

***

## 👤 Members & Activity

**Members** – the people taking part in your loyalty program. The Members module holds each member's details and activity.\
👉 [Members](https://help.openloyalty.io/members-and-activity/members)

**Segments** – groups of members based on their data, transactions or behaviour in the program.\
👉 [Segments](https://help.openloyalty.io/members-and-activity/members/segments)

**Referred Members** – the relationships between referrers (members who send an invitation) and referees (the people they invite).\
👉 [Referred Members](https://help.openloyalty.io/members-and-activity/members/referred-members)

**Transactions** – customer purchases and returns recorded in the program. A transaction can be linked to a member and belong to a sales channel, such as an online store, mobile app or POS.\
👉 [Transactions](https://help.openloyalty.io/members-and-activity/transactions)

**Custom Events** – member actions other than transactions, sent to Open Loyalty through the API, such as a login or a workout. Each type of event is described in a custom event schema.\
👉 [Custom Events](https://help.openloyalty.io/members-and-activity/custom-events)

**Wallets** – where the loyalty units used in your program are stored, such as points or stamps.\
👉 [Wallets](https://help.openloyalty.io/members-and-activity/wallets)

***

## 📣 Campaigns

**Campaigns** – rules that reward members when they meet the criteria you set. There are three types: **Direct** (triggered by a member action, such as a purchase), **Automation** (triggered by a schedule, a birthday or a membership anniversary) and **Referral** (rewarding both the referrer and the referee).\
👉 [Campaigns](https://help.openloyalty.io/campaigns/campaigns)

**Challenges** – goals members work toward by completing specific actions, such as making purchases, logging custom events or referring friends.\
👉 [Challenges](https://help.openloyalty.io/campaigns/challenges)

***

## 🏆 Gamification

**Leaderboards** – rankings that show members in order of their performance on a chosen metric.\
👉 [Leaderboards](https://help.openloyalty.io/gamification/leaderboards)

**Fortune Wheels** – an element of chance: members spin a wheel to receive a randomised prize.\
👉 [Fortune Wheels](https://help.openloyalty.io/gamification/fortune-wheels)

**Badges** – labels you assign to members to recognise a status or behaviour.\
👉 [Badges](https://help.openloyalty.io/gamification/badges)

**Tiers** – levels that group members based on rules you define.\
👉 [Tiers](https://help.openloyalty.io/gamification/tiers)

***

## 🎁 Rewards Redemption

**Rewards** – the benefits members can redeem, such as coupons or material rewards.\
👉 [Rewards](https://help.openloyalty.io/rewards-redemption/rewards)

***

## 🔌 Integrations & Data Exchange

**Webhooks** – notifications Open Loyalty sends to your other systems when a selected event happens.\
👉 [Webhooks](https://help.openloyalty.io/integrations-and-data-exchange/webhooks)

**Imports / Exports** – bringing data into Open Loyalty and taking it out, in bulk.\
👉 [Imports / Exports](https://help.openloyalty.io/integrations-and-data-exchange/imports-exports)

**Collections** – reusable lists of values, such as cities, SKUs or emails, that you can reference in campaign conditions.\
👉 [Collections](https://help.openloyalty.io/integrations-and-data-exchange/collections)

**Product Catalog** – your products (SKUs) inside Open Loyalty, with their name, category, brand, price and attributes, so campaigns can reward specific products or groups of products.\
👉 [Product Catalog](https://help.openloyalty.io/integrations-and-data-exchange/product-catalog)

**Custom Fields** – your own typed fields added to members, campaigns and rewards.\
👉 [Custom Fields](https://help.openloyalty.io/integrations-and-data-exchange/custom-fields)

**Expressions** – Open Loyalty's language for writing campaign conditions and values that the ready-made options don't cover.\
👉 [Expressions](https://help.openloyalty.io/integrations-and-data-exchange/expressions)

***

## ⚙️ Administration

**Tenants** – separate spaces in Open Loyalty, each with its own name, code, currency and members list.\
👉 [Tenants](https://help.openloyalty.io/administration/settings/tenants)

**Admins and Roles** – the people who can use the Admin Panel, and what each of them can view and modify.\
👉 [Admins](https://help.openloyalty.io/administration/settings/admins) and [Roles](https://help.openloyalty.io/administration/settings/roles)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/playbook/introduction/common-concepts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
