> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/tools/budget/review-your-budget-pacing-alerts.md).
# Review your budget pacing alerts
You'll find your budget alerts on the **Audit & budget** screen (for both account-level and budget group alerts).
There are four different budget alerts available, shown with these symbols.
**Overpacing or underpacing**
**Spend threshold reached or missed**
To view the alert details, simply click on the icon.
Within an individual PPC account, you can also find your account-level alerts on the **Budget** > **Manage** screen.
Budget group alerts appear under **Budgets** > **Budget groups**.
{% hint style="info" %}
You can also set up email or Slack notifications for budget alerts. Simply edit an alert and tick **Send me an additional notification..**.
{% 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.adalysis.com/tools/budget/review-your-budget-pacing-alerts.md?ask=&goal=
```
`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.