> 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/technical-guide/data-exports/data-structure-and-types/tiers.md).

# Tiers

The Tiers file contains data on the various tiers.&#x20;

A sample file is provided below:

{% file src="/files/FuTf3a61ExQrUt4eeUUd" %}

**Available Data:**

* **levelId**: Unique ID of the tier
* **tenantId**: ID of the tenant where the tier is created
* **name**: Name of the tier
* **description**: Description of the tier
* **hasPhoto**: Status indicating if a photo is present (true = 1 / false = null)
* **active**: Status indicating if the tier is active (true = 1 / false = null)
* **conditionValue**: Minimum condition to reach the tier&#x20;

{% hint style="danger" %}
**`conditionValue`  is a deprecated field.** Use values from the **`conditions`** column instead.
{% endhint %}

* **rewards**: Rewards or benefits associated with the tier
* **createdAt**: Date when the tier was created
* **updatedAt**: Date when the tier was last updated
* **tierSetId**: ID of the tier set where the tier is created
* **tierSetName**: Name of the tier set where the tier is created
* **conditions:** List of minimum conditions to reach the tier


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/tiers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
