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

# Action

Action is the Campaign workspace where accepted opportunities become rows of work. It operates like a [Grid](/actions/grids.md), so your team can add fields, run [Playbooks](/actions/playbooks.md) and [Workflows](/actions/workflow-concepts.md), review outputs, track publishing, and manage the work tied to the Campaign.

Use **Action** after your team accepts opportunities. The goal is to keep the work connected to the Campaign, instead of moving it into a separate process where impact is harder to measure.

## How Action works

1. Accept opportunities from **Opportunities**.
2. Open **Action** in the Campaign.
3. Open an Action cell to see the approved brief, target page, and included context.
4. Edit the brief in the Action cell if the instruction should change after acceptance.
5. Add the Playbooks or Workflows your team needs to create, refresh, review, or publish the work.
6. Add publishing, ownership, and handoff fields as needed.
7. Run the work from the accepted Action rows.

Each accepted opportunity creates one Action row. The row is the durable record of the approved action, not only a page or prompt cell.

## What an Action row contains

| Part                  | Use it for                                                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Action cell**       | The approved brief, target page, and supporting context carried over from the opportunity.                                  |
| **Playbook columns**  | Repeatable content tasks, such as refresh briefs, content updates, or review steps. See [Playbooks](/actions/playbooks.md). |
| **Workflow columns**  | Lower-level workflow processes tied to the accepted action. See [Workflows](/actions/workflow-concepts.md).                 |
| **Publishing fields** | CMS details, URLs, and handoff notes. See [Publish to CMS from Grid](/actions/grids/publish-to-cms-from-grid.md).           |

## Action JSON shape

When you map an Action column into a Playbook or Workflow, AirOps passes a structured object with the following shape:

An Action object contains these fields:

| Field                   | Shape            | Purpose                                                             |
| ----------------------- | ---------------- | ------------------------------------------------------------------- |
| `action_item_id`        | Integer          | The Action record's ID.                                             |
| `source_opportunity_id` | Integer          | The Opportunity that created the Action.                            |
| `rationale`             | String           | The editable brief for the work.                                    |
| `target_page`           | Object or `null` | The page to refresh. It is `null` for a page-creation Action.       |
| `contexts`              | Array            | The supporting pages or prompts included during Opportunity review. |

The `target_page` object includes `web_page_id`, `url`, and `brand_kit_id`.

Each item in `contexts` includes:

* `id`: The context ID.
* `rationale`: Why the context supports the Action.
* `position`: The context's order.
* `resource`: The supporting page or prompt.

A prompt resource includes its `type`, `id`, prompt text, topic, and tags. A page resource includes its `type`, `id`, page URL, folder, and topics.

The Campaign action type, such as `page_refresh` or `page_creation`, is configured on the Campaign. It is not included in the current Action execution payload.

## Track content updates

Use the **Track Content Update** step in the Playbook or Workflow that publishes or refreshes the page. Older workflows may refer to this step as **Track Event**.

The step records a content update in AirOps so Measurement can show when the work happened alongside page performance. It does not activate the Measurement tab. Measurement is available before Action rows or tracked events exist.

### Configure the step

1. Add **Track Content Update** after the step that publishes or refreshes the page.
2. Choose the event type:
   * **Page Published** for a new page.
   * **Page Refreshed** for an existing page.
3. Pass the final public URL of the page.
4. Use the URL from the Action row or the publishing result so the event matches the page that changed.
5. Run the step only after the content is live.

The URL must be the canonical page URL. Do not include a trailing slash or query parameters. AirOps uses the URL's domain to match the event to a Brand Kit.

### Make sure Measurement can use the event

* Use the live page URL, not a preview, staging, or CMS editor URL.
* Use **Page Refreshed** when updating an existing page and **Page Published** when creating a new page.
* Keep the tracked URL consistent with the page URL in the Action row.
* Confirm that the domain belongs to the Campaign's Brand Kit.
* Check the page's content changes in Measurement after the workflow runs.

Track Content Update events help you compare page performance before and after the work. They do not replace the Action row, page scope, or connected Google Search Console and Google Analytics data.

## Good Action setup

A good **Action** setup matches the Campaign objective. Add the columns your team needs to complete the work, but avoid turning **Action** into a general project tracker.

For a page refresh Campaign, **Action** might include a refresh Playbook, CMS fields, and publish details. For a page creation Campaign, **Action** might include a brief Playbook, supporting-source fields, and publishing notes.

Keep the Action brief specific enough that a Playbook or Workflow can use it. If the instruction is still too broad, edit it in the Action cell before you run the work.

## Examples

### Page refresh Campaign

Use **Action** to refresh accepted pages from the Campaign:

1. Open the Action cell and confirm the target page and brief.
2. Add the Playbook or Workflow that drafts refresh recommendations.
3. Add publishing fields for the CMS handoff or publish URL.
4. Add ownership fields for the teammate responsible for the work.
5. Track each page through review and publishing.

### Page creation Campaign

Use **Action** to create content that supports accepted prompts:

1. Open the Action cell and confirm the included prompts.
2. Add the Playbook or Workflow that turns the brief into a draft page.
3. Add fields for supporting sources and publishing notes.
4. Track whether each accepted action has shipped.


---

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