> 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/export-customers-transaction-history.md).

# Export customer's transaction history

To export a customer's transaction history, navigate to the customer's profile.\
\
Click "Export transaction history", and it will prompt a download of the .csv.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2Fm36OPXkha4pgw3JtTgj3%2FScreenshot%202026-05-05%20at%202.37.01%E2%80%AFPM.png?alt=media&amp;token=d9b09124-a999-434a-9143-a27194ef4923" alt=""><figcaption></figcaption></figure>

The file contains the following fields:

* Transaction ID
* Transaction Datetime
* Title
* Classification (EARN or REDEEM)
* Points Each
* Quantity of Each
* Total Transaction Points
* Transaction Source
* Transaction Status
* Transaction Reference ID
* Voucher ID
* Business ID
* Business Name
* Location ID
* Location Name
* External Location ID
* Perk ID
* Perk TItle
* Perk Use\
  Perk Class
* User ID
* User Email
* Created Datetime
* Last Modified Datetime
* Staff ID
* Staff Email


---

# 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/export-customers-transaction-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.
