# Review and approve staged changes

> How Maven stages Google Tag Manager changes for a client, what you see at the review checkpoint (the exact staged changes and QA evidence), and how to approve or reject them.

Source: https://mavendata.ai/docs/tag-management/approvals

Every tracking change Maven makes for a client goes through a review checkpoint. Maven prepares the change, stages it in the client's GTM container and runs QA. Then it stops and waits for you. Before anything is published, you see the exact staged changes and the QA evidence, and a person with the right permission has to approve that exact checkpoint. Maven never auto-publishes.

## How a change moves through Maven

| Step | What happens | Publishes anything? |
|---|---|---|
| Submit | You describe the work as a tagging request from your AI tool. | No |
| Prepare | Maven checks readiness, then does the work: stages the change, runs browser journeys and provider checks, and runs QA. | No. Preparation never authorizes publication. |
| Review | You read the checkpoint: the staged changes and the QA evidence. | No |
| Decide | You approve or reject that exact checkpoint. | Only on approval |

All of this runs through the `request` tool in Claude, ChatGPT or any AI tool connected to Maven. See [Agent workflows](https://mavendata.ai/docs/mcp/workflows) for the full calls.

## Review the checkpoint

1. Ask your assistant to show the request that's waiting for review, for example "Show me what's staged for Acme's tracking request." It reads the checkpoint with `request` → `review`.
2. Check the staged changes. Each entry shows the action (create or update), what kind of GTM item it is (such as a tag or trigger), and its ID and name.
3. Check the QA evidence:
   - The overall QA outcome: pass or fail.
   - Whether the change was confirmed at runtime.
   - Coverage: for each page and element tested, which vendor and event fired, where it was sent, and how many times.
   - Links to the evidence Maven collected.
4. If something looks wrong, don't approve it. Reject it, or add context to the request so Maven prepares it again.

Requests submitted this way never delete items from the client's container. Where a request needs to remove a tag, Maven stages it as paused instead.

```prompt
Show me what's staged for Acme's tracking request, with the QA evidence.
```

## Approve or reject

When you're satisfied, tell your assistant your decision in your own words, for example "Approved: publish the staged LinkedIn conversion for Acme." The assistant records it with `request` → `decide`. Your statement is kept in the approval audit trail.

- **Approve**: Maven publishes exactly the changes you reviewed.
- **Reject**: nothing is published, and the request doesn't go ahead.

The approval is tied to the exact checkpoint you reviewed. If the request changes after you looked at it (new context, a fresh preparation, or different staged changes), the old approval no longer applies, and you need to review the new checkpoint.

```prompt
Approve the staged tracking changes for Acme.
```

## Who can approve

Only a signed-in person whose Maven connection has tracking write access (or admin) can approve. An AI assistant can't approve on your behalf, and your assistant should never decide for you. Approvals are recorded against the person who made them. See [MCP security](https://mavendata.ai/docs/mcp/security).

## FAQ

**Can Maven publish a GTM change without approval?** No. Staging and QA happen without approval. Publishing never does.

**What if the QA fails?** The checkpoint shows the failed checks. Don't approve it. Ask Maven to fix the issue and prepare the request again.

**Can I see what's waiting across all my clients?** Yes. Ask your assistant to list requests and their status for each workspace.

## Related

- [Connect your tag manager and check tracking](https://mavendata.ai/docs/tag-management)
- [Server-side conversions and consent](https://mavendata.ai/docs/tag-management/server-side)
- [MCP operation reference](https://mavendata.ai/docs/mcp/reference)
