> For the complete documentation index, see [llms.txt](https://handbook.spend.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.spend.market/markets/resolution-metrics.md).

# Resolution Metrics

Every market resolves on exactly one of four metrics, always stated on the market page. They exist because different economic questions need different lenses. A 10% rise in spend could mean more people showed up, the same people spent more per visit, or prices moved. Four metrics let you isolate which.

The four resolution metrics are:

1. [Transaction Count](/markets/resolution-metrics/transaction-count.md)
2. [Unique Purchasers](/markets/resolution-metrics/unique-purchasers.md)
3. [Aggregate Spend](/markets/resolution-metrics/aggregate-spend.md)
4. [Average Transaction Value (ATV)](/markets/resolution-metrics/average-transaction-value-atv.md)

> Consumer-facing language follows the group: "subscribers" for AI and streaming, "members" for gyms, "participants" for events, "customers" for retail. The rules are always specific. ATV runs cleanly in merchant-vs-merchant matchups; in Target format it can also run on a single group. All relevant market definitions can be found within each market's description.


---

# 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, and the optional `goal` query parameter:

```
GET https://handbook.spend.market/markets/resolution-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.