> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/upgrade-promo-code-monitoring.md).
# Upgrade Promo Code Monitoring
Take the PXA course
Need automated daily scanning and alerts to notify you of any promo code violations? **Upgrade** and get the following benefits with impact.com’s Promo Code Monitoring:
* See where publishers are promoting your codes - even if they aren’t part of your program.
* Remediate issues directly from the platform - or automate to save even more time.
* Shut down the use of expired and unauthorized codes.
1. From the left navigation bar, select  **\[Protect]** → **Monitoring** → **Promo Code**.
2. Select **Get Promo Code Monitoring**.
3. In the upgrade window, select **Get Standard**.
4. Review the details of your selection in the confirmation summary.
5. Select **Confirm** to complete your upgrade.
[Learn more](/brand/what-would-you-like-to-learn-about/account-administration/account-settings/subscription-add-ons/subscription-add-ons-explained.md) about how add-on upgrades work on impact.com!
---
# 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.impact.com/brand/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/upgrade-promo-code-monitoring.md?ask=&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.