> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/loyalty-program/loyalty-program-history.md).

# Loyalty Program History

Review changes made to loyalty-program perks.

Perkville records changes made to loyalty-program perks so administrators can understand how program configuration has changed over time.

The history includes perk creations, edits, deactivations, and reactivations recorded after this feature became available. It does not reconstruct changes made before history tracking was enabled.

## View history for a specific perk

1. From the Dashboard, open **Loyalty Program**.
2. Select the perk you want to review.
3. Use the history link or icon in the upper-right area of the perk edit page.

The perk-specific view shows the recorded changes for that perk, including who made the change and what changed when that information is available.

## View history across the loyalty program

1. From the Dashboard, open **Loyalty Program**.
2. Select **View program history** near the top of the page.
3. Use the available filters to narrow the results. For example, you can filter by perk ID, the person who made the change, or the type of change.
4. Select **Export CSV** when you want to download the history for further review or analysis.

Each entry identifies the perk, who changed it, and the change that was recorded. Expand an entry when you need to review the configuration details associated with that event.

For general instructions on creating, editing, deactivating, and reactivating perks, see [Loyalty Program](https://docs.perkville.com/features/settings/loyalty-program.md).


---

# 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://docs.perkville.com/features/settings/loyalty-program/loyalty-program-history.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.
