Skip to main content

Change Requests - User Guide

Written by Radhika Shenoy

What is It?

Changes suggested by an AI assistant through the Optmyzr MCP — for example, when you ask Claude to add keywords — don't apply to your account directly. Instead, they're staged as a change request, which then gets checked against your account's policy guardrails, then reviewed and applied by a person. This article explains how change requests work, how to review and apply them, and how policy guardrails are configured.

Where to Find It?

Go to Utilities → Change Requests to see every change request raised on the account, including ones you raised yourself. You can also click directly into a request from its notification in Claude.

Each request shows the account, campaign, and ad group it applies to, and the type of change being suggested (for example, a keyword addition).

How It Works

1. You ask your connected AI assistant (e.g., Claude, via the Optmyzr MCP) to make a change — for example, suggest keywords to add.

2. Optmyzr stages the suggestion as a change request instead of applying it immediately.

3. The change request is checked against your account's policy guardrails.

4. A person on your team reviews the request, change by change — commenting, editing, approving, or rejecting each one.

5. Once review is complete and policy checks pass, the reviewer applies the request (immediately, if they have Apply access, or after a team member with Apply access approves it).

Reviewing a Change Request

You'll see four different tabs on the Change Requests page:

  • All Requests

  • My Requests

  • Pending my Approval

  • Closed

The changes list can be viewed grouped by Entities (account → campaign → change) or by Actions, and you can filter or search within it. You can also run AI Review to have Optmyzr's AI review the batch of changes before you go through them yourself, or use Bulk Remove to remove multiple changes at once.

Each individual change shows what it is (for example, a negative keyword) and the action being taken (for example, New), along with the exact value and match type. Click Why? next to a change to see the reason it's being suggested.

For any individual change, you can:

  • Comment on it

  • Edit it before it's applied

  • Delete it

Next to each change, you'll also see why it's being suggested, if there's a policy violation involved in making the change. You can choose to skip the change if you do not want to continue with a violation.

Once you've gone through the individual changes, the request shows a policy-check summary — for example, "All policy checks passed, no violations" — along with an Apply action that applies every approved change in the request at once.

Applying a Change Request

You will be able to apply changes only if you have the right access level. If you do not have access to make changes in the ad account, you can only submit a change request for review. What you can do next depends on your Apply access:

  • With Apply access: you can apply the request's changes directly once review is complete.

  • Without Apply access: you submit the request to a team member who has Apply access. The changes only go live once that person reviews and approves them.

Policy Guardrails

Policy guardrails are rules every change request is checked against before it can be applied. You'll find them under Change Review → Policy settings, organized into an organisation-wide policy sheet grouped by category — for example, Bids, Keywords, and Account-wide.

A default set of policies comes pre-configured by Optmyzr — you can turn any of them on or off, edit their thresholds, or add your own.

  • Right now, every guardrail behaves as a warning: a change that violates one is flagged and needs explicit approval to proceed, but isn't blocked outright.

  • Only the parent user can add new policies or edit existing policy configurations.

  • Guardrails can be set at the broadest level (all accounts, all platforms) and overridden for a specific platform or a specific set of accounts. When more than one setting could apply, the most granular one wins — an account-level override beats a platform-level override, which beats the all-accounts-and-platforms default.

Change Requests - Supported Entities

Change requests currently support adding positive and negative keywords. Support for additional entity types (such as campaigns, budgets, and ad copy) is coming soon.

Did this answer your question?