> 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.md).

# Campaigns

Campaigns are how AirOps measures the impact of your AI search work.

Use a Campaign when you want one place for the objective, the recommended actions, the work that ships, and the signals that tell you whether the effort is working.

## What a Campaign is

A Campaign is the end-to-end effort to impact your AI search performance. It brings the strategy, work, and measurement for that effort into one place.

* **Objective:** The outcome you want to improve.
* **Scope:** The Brand Kit, topics, and folders or prompt tags the Campaign should evaluate.
* **Opportunities:** Recommended actions with a brief and supporting context.
* **Action:** The accepted work your team creates, refreshes, reviews, or publishes.
* **Measurement:** The performance signals that show whether the work changed visibility, citations, sentiment, traffic, or share of voice.

## How teams use Campaigns

Use Campaigns to manage content work from priority through measurement. A Campaign helps your team:

* Start with a priority from Insights, such as a visibility gap, citation issue, sentiment theme, or traffic trend.
* Turn that priority into opportunities for pages or prompts.
* Move accepted opportunities into **Action** for creation, refresh, review, and publishing.
* Keep the work tied to the same objective from strategy through execution.
* Measure what changed after the work ships.

## Campaign tabs

| Tab               | Use it to                                                                           |
| ----------------- | ----------------------------------------------------------------------------------- |
| **Opportunities** | Review recommended actions, add opportunities manually, and accept or decline work. |
| **Action**        | Run accepted work in a Grid-style workspace.                                        |
| **Measurement**   | Track page performance, visibility, and sentiment for accepted work.                |

For common questions about Campaign versions, Opportunities, Action, and Measurement, see the [Campaigns FAQ](/campaigns/faq.md).

## What teams learn

Campaigns help your team decide where to invest more effort, where to double-check the work, and where to cut back. Use Measurement to find:

* Actions that improved AI visibility, citations, sentiment, traffic, or share of voice.
* Work that needs another review because the expected signal did not move.
* Efforts that should be narrowed, paused, or stopped.
* Patterns your team can use to shape the next round of opportunities.


---

# 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/campaigns.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.