> 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/manage/placements/optimize-your-placements.md).

# Optimize your placements

{% embed url="<https://youtu.be/4EYu2uuEmUU>" %}

Adalysis helps you view and exclude placements, so your ads only appear in the right places. This keeps your budget focused on what works, improving performance and efficiency.

### **Automatic placements**

Review your placements under **Manage** > **Placements** > **Automatic** within an individual account.

Google Ads only displays placements at the ad group level. As the volume of data is often small, this can be tricky to analyze. This is why Adalysis also aggregates placement data at the campaign and account level.

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

You can filter the data to identify **poorly converting placements** and other criteria.

<figure><img src="/files/egCM2P3p1JQ6vZ7F3JWi" alt="" width="496"><figcaption></figcaption></figure>

{% hint style="info" %}
The prebuilt filter changes from ad group to campaign and account placements depending on the active tab.
{% endhint %}

<details>

<summary>Prebuilt placement alerts</summary>

**New negative placements suggestions**: Adalysis also offers a prebuilt alert matching the filter above. You can customize the default settings under **Audit** > **Audit** s**ettings** > **Prebuilt** > **Placements**.

</details>

### **Exclusions**

View your exclusions at the ad group, campaign, account, and list-level, under **Manage** > **Placements** > **Exclusions**. This screen offers three tools, with corresponding prebuilt alerts:

#### Mobile app exclusions

In Google Ads, managing exclusions can be time-consuming. This is why Adalysis offers exclusions by category. You can exclude all mobile traffic, or choose specific phone types or app categories. Exclusions can also be applied at the account or campaign level.

<figure><img src="/files/ac8yJVYCPQeQZaAcMRNe" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/hOQ7zfTtGg8kirc6QMHS" alt="" width="563"><figcaption></figcaption></figure>

#### Content categories

With this tool, you can exclude placements based on content categories. This is a fast way to protect your brand from appearing in unsuitable spots.

* Sensitive content
* Content types, including parked domains
* Content label, including audience types

#### Moving exclusions

Use this migration tool to easily shift exclusions between campaigns or change the level at which they're set. For example, you can select exclusions set at the campaign level and move them to the account level. This prevents all your other campaigns from showing in these placements.

Adalysis also supports exclusion lists.

<figure><img src="/files/lr67UadooALDtCSYRbWZ" alt="" width="563"><figcaption></figcaption></figure>

The Adalysis audit alerts will automatically suggest new exclusions. You can edit your alerts in **Audit** > **Audit settings** > **Prebuilt** > **Placements** and enable [auto resolves](/tools/audit/how-to-auto-resolve-alerts.md). For example, you may want to exclude placements once they meet defined thresholds.

<details>

<summary>Prebuilt exclusions alerts</summary>

[Display campaigns that don't exclude mobile app traffic](#mobile-app-exclusions) (under **Campaigns**)

[Display campaigns that don't exclude sensitive content](/tools/audit/prebuilt-alert-list/placements/sensitive-content-label-exclusion.md) (under **Campaigns**)

New negative placement suggestions from aggregated campaign data (under **Placements**)

New negative placement suggestions from aggregated account data (under **Placements**)

</details>


---

# 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/manage/placements/optimize-your-placements.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.
