> 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/customers/custom-attributes.md).

# Custom attributes

Custom attributes let you control which customers can redeem specific [rewards](https://docs.perkville.com/features/redeeming-rules/custom-rewards.md) or enroll in [challenges](https://docs.perkville.com/features/challenges.md). This allows you to create targeted incentives and gamified experiences for different customer segments.

Custom attribute values will display on your customers' profile pages.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FXuMzmeLB5yGHICS43sCF%2FScreenshot%202025-07-01%20at%2010.36.23%E2%80%AFAM.png?alt=media&amp;token=bf9a82b7-c2cf-4c34-8a4c-6577cc913179" alt=""><figcaption><p>You can require a custom attribute to allow a customer redeem for a reward or participate in a challenge</p></figcaption></figure>

## Custom attribute breakdown

There are custom attributes and then values associated with that custom attribute. For example, **VIP member?** might be your customer attribute and the values for the customer attribute would be **VIP** and **Not VIP**.

## How to setup an custom attribute

:mega: Reach out to **Perkville support** to configure a custom attribute for your loyalty program.

## Applying custom attributes

Once custom attributes have been set up for your loyalty program, they will be accessible from the customers' pages.\
\
Custom attributes can be added, modified, and removed via the customer's page.

Any existing custom attributes will be seen in the Customer Attributes dropdown at the top of the page.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FjsvPeiqN0iCb9gns1Mfh%2FScreenshot%202026-05-05%20at%202.20.36%E2%80%AFPM.png?alt=media&amp;token=0ba36be8-dde8-433b-b7d8-c1db87aff146" alt=""><figcaption></figcaption></figure>

\
Click on "Add/Modify Attributes" to add, modify, or remove an attribute from a customer.

Pick the appropriate attribute and value from each dropdown and then hit Save.

{% hint style="info" %}
To remove an existing attribute from a customer, select the \*None\* option and hit Save.
{% endhint %}

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FBUNAUlrn0HwjEV4JMqbM%2FScreenshot%202026-05-05%20at%202.23.57%E2%80%AFPM.png?alt=media&amp;token=6588dae9-ea5f-408c-bf6d-d8dc04534c7d" alt=""><figcaption></figcaption></figure>

The Attribute History page will log any changes to an attribute made by a staff member for easier tracking.\
\
Click on "View Transactions" to return to the customer's page.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2F7CEu8g0sfQhjZmDPolXy%2FScreenshot%202026-05-05%20at%202.26.13%E2%80%AFPM.png?alt=media&amp;token=741f6c8a-20f0-472b-bdf4-97d12036abee" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The Perkville team can assist in setting up an automation to apply and remove customer attribute values
{% endhint %}


---

# 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/customers/custom-attributes.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.
