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

# Overview

Campaigns are how AirOps measures the impact of your AI search work. Use them to connect a priority from Insights, the pages or prompts that need attention, the work your team takes action on, and the Measurement view that shows what changed.

Use Campaigns to understand whether your content actions are working. After work ships, Campaign measurement helps you see where performance improved, where a result needs another look, and where to cut back because the action is not moving the metric.

## What a Campaign Is

In practice, a Campaign brings the parts of an AI search effort into one place:

* **Objective:** The AI search or marketing outcome you want to improve.
* **Scope:** The pages or prompts the Campaign should evaluate.
* **Opportunities:** Recommendations for where your team should act.
* **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.

## 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:

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

The question should be specific, self-contained, and written in natural language.
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.