> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/playbooks/tools/paid-ads.md).

# Paid Ads

Paid Ads Tools help Playbooks inspect advertising performance before creating reports, campaign briefs, or optimization recommendations.

## Tools

### OpenAI Ads

Retrieve insights from your OpenAI Ads account, including account, campaign, ad group, and ad-level performance.

Use **OpenAI Ads** when a Playbook needs paid performance data before writing a report, summarizing campaign health, or recommending budget and creative changes. The Tool can retrieve account-level, campaign-level, ad group-level, and ad-level insights.

## How to Configure

1. Open the Playbook editor.
2. Type `/` in the Section where ads performance should be analyzed.
3. Select **OpenAI Ads**.
4. Connect the required OpenAI Ads authentication if prompted.
5. Add the account, campaign, ad group, ad ID, date range, and metrics the Playbook should inspect.

## Parameters

| Tool           | Required context             | Optional guidance                                                                                                                            |
| -------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **OpenAI Ads** | Connected OpenAI Ads account | Add campaign ID, ad group ID, ad ID, date range, daily breakdown, and target metrics such as impressions, clicks, CTR, spend, or conversions |

## Examples

```markdown
Use **OpenAI Ads** to compare campaign performance for the last 30 days. Return spend, CTR, conversions, and the strongest optimization recommendation.
```


---

# 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.airops.com/actions/playbooks/tools/paid-ads.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.