> 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/audit/prebuilt-alert-list/placements/mobile-apps-exclusion.md).
# Mobile apps exclusion
Mobile app traffic can be of very low quality and many advertisers want to exclude it completely. Adalysis will alert you to any campaigns that don't completely exclude mobile app traffic.
You'll see the alert on your **Audit alerts** screen. Click it for a list of affected campaigns. You can then exclude all mobile apps or specific types, both at the account level or for individual campaigns.
{% hint style="warning" %}
**Important:** Account-level exclusions will override campaign-level exclusions.
{% endhint %}
Alert pop-up
Expand the account or campaign-level exclusions. Then, select the types of apps you don't want to show your ads in and click the **Exclude selected apps** button:
#### Account level
#### Campaign level
---
# 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/audit/prebuilt-alert-list/placements/mobile-apps-exclusion.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.
