> 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/reports/transaction-quantities-by-location.md).

# Transaction Quantities by Location

The Transaction Quantities by Location Report is a detailed document that provides insights into the number of transactions at locations within a specified period. This report will return a mapping between all selected locations and all selected perks, so you can get a detailed overview of how perks are performing at various locations.

#### Filter for the Transaction Quantities by Location Report

Before running the report, you can apply the following filters to customize the data:

* **Transaction Date Range**: Specify the start and end dates for the transactions you want to include. These dates represent when the transaction happened in the source system.
* **Last Modified Date Range**: Set the date range for when transactions were last modified.
* **Locations**: Select the specific locations for which you want to view transactions. You can run the report for all locations or narrow it down to specific locations.
* **Location Groups**: Choose a location group (e.g. you can create groups for franchises, regions, etc) to view the transactions for locations within a given group.
* **Earn Perks**: Filter transactions based on earning perks, including standard perks, bonus perks, and inactive perks.
* **Redeem Perks**: Filter transactions based on redemption perks, including standard redemptions, instant rewards,  referral offers, and inactive perks.

{% hint style="info" %}
At least one perk must be selected for this report.
{% endhint %}

* **Status**: Include transactions based on their status, such as active or voided.

#### Columns in the Transaction Quantities by Location Report

* **Location Name**: The name of the location at which the transactions took place.
* **POS Location ID**: The Point of Sale ID for the location in question (e.g., ABC Club Number, MindBody ID, ASF Club Number).
* **\[Column for each selected perk]**: Each column title will include the name and ID of the perk. The value will be the total quantity earned/redeemed at the listed location.

### Generating the Report

To generate the **Transaction Quantities by Location** **Report**:

1. Navigate to the **Reports** section in your Perkville dashboard.
2. Select **Transaction Quantities by Location** from the list of available reports.
3. Apply the desired filters and choose your date range.
4. Click **Run Report** to export the data as a CSV file for further analysis.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/features/reports/transaction-quantities-by-location.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 `build a script that syncs our docs to a CMS` 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.