> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/reports/discount-codes-report.md).

# Summary of Discount Code Usage

Do your clients use discount codes when signing up? In the *Reports* tab you can check how many times each code was used — and in what time period.

## How to generate the report

1. Go to ***Reports*** → ***Other*** → ***Discount codes***.
2. Set the date range you want to analyse.
3. Click ***Generate report***.

{% hint style="info" %}
The *Discount codes* section only appears in the *Reports* tab if at least one discount code is active. For more information, see the [discount codes article](/en/online-sign-ups/discount-codes.md).
{% endhint %}

![Animated screenshot showing the Discount codes report being generated](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-70359b24fcf273255f688fd45dec536a330d9692%2FZrzut%20ekranu%202026-05-26%20124941.png?alt=media)

## What the report shows

The report shows how many times each code was used during the selected period. Only codes that were used at least once are displayed. Codes deleted from the system are not included.

To find codes that became inactive, set the appropriate date range — historical data is available even after a code has been deactivated.


---

# 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://help.activenow.io/en/reports/discount-codes-report.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.