> 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/faq.md). # Campaigns FAQ Answers to common questions about AirOps Campaigns Campaigns connect an AI search priority to recommended work, execution, and measurement. Use this FAQ to understand Opportunities, Action, and Measurement. ## Why does my Campaign look different? If you are comparing an older Campaign with a newer one, the newer Campaign may include contextual Opportunities, Campaign Actions, and the updated Measurement experience. ## What is the difference between an Opportunity and an Action? An **Opportunity** is a recommendation for work. It includes a brief, and it may include a target page and supporting prompts or pages. Your team reviews the recommendation before accepting or declining it. An **Action** is the accepted work that appears in the Campaign's Action workspace. It keeps the approved brief and context, and gives your team a row where you can run Playbooks or Workflows and track publishing. ## When does Measurement become available? Measurement populates after the content associated with an accepted Action is published through a connected CMS or recorded with the **Track Content Update** step. The **Measurement** tab may be visible before then, but the Campaign needs a recorded publication or refresh to show the resulting content change and compare performance. See [Measurement](/campaigns/measurement.md) for the sections and filters. ## How do supporting contexts affect Measurement? Choose the supporting prompts or pages that belong to the action during Opportunity review. Included context is carried into **Action** and measured in **Measurement**. Removed context is not measured. ## How do I track a page publication or refresh? Add the **Track Content Update** step to the Playbook or Workflow that publishes or refreshes the page. Use **Page Published** for new content and **Page Refreshed** for an existing page. Pass the final public URL after the content is live so AirOps can associate the update with the correct Brand Kit and page. See [Action](/campaigns/action.md) for configuration guidance. ## Can I edit a Campaign after publishing? If you have Campaign update permission, you can edit **Opportunity Criteria** in **Campaign settings** or through Quill. Save the changes before generating opportunities. Future generation runs use the new criteria; existing opportunities stay unchanged. Archived Campaign criteria are read-only. You can also generate opportunities, add opportunities manually when available, and manage triggers. ## Why is a Measurement section empty? Check the following: * The selected date range includes the period you want to review. * The Measurement filters match the Campaign's configured topics, pages, or prompts. * The required Google Search Console or Google Analytics integration is connected for search or traffic metrics. * The pages or prompts are still available in the Brand Kit. If the section remains empty, review the Campaign scope and the data source that powers the metric. --- # 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/faq.md?ask=&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.