> For the complete documentation index, see [llms.txt](https://docs.indinite.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.indinite.co.uk/tracking-sales.md).

# Tracking Sales

1. ## Click on Track Sales

<figure><img src="/files/qoToRcF7M77kQHoN6CPm" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/r3Z7r6ykZsJP6qYvFx2m" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/CPbslezN6FWZPscSxJcX" alt=""><figcaption></figcaption></figure>

### 📈 What You’ll See

* **Total Orders** → How many purchases happened.
* **Tickets Sold (per type)** → See exactly how many Early Birds, VIPs, or General tickets are gone.
* **Remaining Tickets** → What’s left in stock.
* **Revenue** → How much money you’ve made (before Indinite’s platform fee).
* Attendees → Total Attendees

### How to Use This Info

* If **tickets are selling fast** → Add more tiers (like Late Bird or Door Price).
* If **tickets are stuck** → Push marketing harder, or drop an early discount.
* If **VIPs are sold out** → Congrats, people want the fancy stuff.

{% hint style="success" %}
👉 That’s the lowdown on **Sales Tracking**. It’s your scoreboard — check it often, but don’t stress too much. The party always fills up closer to the date 🎉.
{% 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 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://docs.indinite.co.uk/tracking-sales.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.