> 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/campaigns/ads.md).

# Ads Opportunity Campaigns

Find ChatGPT ad opportunities from competitor activity and act on them with enabled Campaigns.

An Ads opportunity Campaign uses observed ChatGPT ad activity to find topics and prompts where competitors advertise and your brand has a coverage gap. Review the evidence, accept relevant opportunities, and use the Action Grid to prepare ad variants with a Playbook.

{% hint style="info" %}
The **Ads** Campaign type requires separate enablement. Ad creation also requires access to the OpenAI Ads Playbook write tools and a connected ad account. Contact your AirOps team about access and the appropriate Action Grid and Playbook setup.
{% endhint %}

An AirOps Campaign organizes opportunity discovery and execution. The ad campaigns created in ChatGPT Ads Manager hold the budgets, ad groups, and ads used for delivery.

## How to Configure

1. [Create a Campaign](/campaigns/create-a-campaign.md) with the **Ads** action type where available.
2. Select the **Brand Kit** and configure the topics and prompt tags in scope.
3. Add opportunity criteria describing the audiences, products, and claims you want the Campaign to prioritize.
4. Review and publish the Campaign, then generate opportunities.
5. Open each opportunity to inspect the diagnosis, supporting evidence, competitor references, and recommended ad strategy.
6. Accept relevant opportunities into **Action**. Each accepted opportunity becomes one Grid row.
7. Review the connected Playbook's inputs and run it to prepare ads. Where write tools are enabled, review the paused resources before activation.

## Parameters

| Setting                      | Purpose                                                                  |
| ---------------------------- | ------------------------------------------------------------------------ |
| **Brand Kit**                | Supplies brand context and the tracked ChatGPT prompt data.              |
| **Topics / Prompt tags**     | Define the prompt scope for discovery.                                   |
| **Opportunity Criteria**     | Describe what to prioritize or exclude.                                  |
| **Action Grid and Playbook** | Define how accepted opportunities become ad work.                        |
| **OpenAI Ads connection**    | Authorizes enabled tools to create resources in the intended ad account. |

## Review the evidence and output

Discovery looks for competitor ad activity that supports a coverage-gap opportunity. A lack of supporting observations can result in no opportunities.

One opportunity can produce an ad group and multiple ad variants. Those outputs remain associated with the same opportunity, prompts, and topic; they do not each become a separate opportunity row.

Use [Ads Performance](/insights/ads.md#performance) to review delivery results from the connected account. Observed competitor activity helps inform a test, but it does not reveal competitor spend or prove that the same approach will perform for your brand.

## Example

```
Find ChatGPT ad opportunities for our Brand Kit in the project-management
topic. Prioritize prompts where tracked competitors advertise and our brand
has no observed ad coverage. Include the observed creatives and prompts as
evidence. Recommend copy grounded in our approved product claims.
```

Review each opportunity's evidence and proposed message before running its Action Grid row. A Playbook can draft several variants for review while preserving their connection to the original opportunity.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/campaigns/ads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.