> 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/keywords/keywords-generating-expensive-conversions.md).

# Keywords generating expensive conversions

Adalysis will alert you to keywords that have a higher cost per conversion than their ad group average. You'll see the alert on your **Audit alerts** screen. Click it for a list of affected keywords and cost per conversion data. 

{% hint style="warning" %}
**Important:** We exclude keywords with bidding changes in the analyzed time frame. For campaigns using automated bidding strategies, this means no recent target CPA or target ROAS updates. This means you don't get alerts for keywords with higher cost/conversion due to bidding changes.
{% endhint %}

### Customizing your alert

By default, Adalysis will check for keywords with twice the average cost/conversion compared to their ad group. Go to **Audit** > **Audit settings** > **Prebuilt** > **Keywords** to change these conditions and set conversion thresholds for the alert.

You can also choose whether to track results based on **conversion value/cost** or **all conversion value/cost**.

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

### Investigating the performance trend

For manual bidding campaigns, use the [Performance Analyzer ](/tools/performance/root-cause-analysis-with-the-performance-analyzer.md)to identify the factors behind the increased cost/conversion. This may include a low conversion rate or high CPC. Look at related metrics such as impression share and conversion volume before deciding to decrease bids.

In campaigns with automated bidding, we recommend separating poorly performing keywords into different ad groups or campaigns, in bulk. This means you can set different target values.


---

# 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/keywords/keywords-generating-expensive-conversions.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.