What is It?

Changes suggested by an AI assistant through the Optmyzr MCP don't apply to your account directly. For example, if you ask Claude to add keywords, those keywords aren't added right away. Instead, each suggestion is saved as a change request. The request is checked against your account's policy guardrails, and then a person on your team reviews and applies it. That person can approve these changes on the Change Requests page in Optmyzr or directly from the MCP.

This article explains how change requests work, how to review and apply them (in Optmyzr or from the MCP), and how policy guardrails are set up.

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.

Note: You can approve a request on the Change Requests page or directly from your AI assistant. You don't have to switch between the chat and the page. Every change from the AI assistant still creates a change request, so you keep the full record and review history on the Change Requests page.

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. They can do this on the Change Requests page or directly in the AI assistant chat.

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.

You can manage a change request from start to finish without switching to Optmyzr. This is especially useful if you manage an account alone and review your own changes.

You can review and approve change requests either on the Change Requests page or directly through the Optmyzr MCP. You don't have to switch between the two views. The assistant never approves anything on its own. It always asks you and uses your answer.

Every change from the AI assistant still creates a change request, so you keep the full record and review history on the Change Requests page.

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 - What Can Be Changed

Change Requests supports six ad platforms: Google Ads, Amazon, Microsoft Ads, Yahoo, Meta, and LinkedIn. The entities and actions you can change depend on the platform.

Where you can raise change requests

You can raise change requests from three places, and all of them support the same changes:

An AI assistant (Claude, ChatGPT, or any assistant connected through the Optmyzr MCP)
Sidekick, in Optmyzr or in Slack
The Optmyzr UI

Supported changes cover campaigns, ad groups, ads, keywords, negative keywords, asset groups, product groups, product targets, bid modifiers, campaign criteria, shared budgets, and Google Ads recommendations. What's available for each entity depends on the platform. The table below shows what's supported where.

List of Entities, Actions, and Platforms Supported

Note: 'Remove' actions are called out separately because they can't be rolled back. Review these changes carefully before applying them.

Entity	Action
Campaign	Create	✅	✅	❌	❌	❌	❌
	Enable	✅	✅	✅	✅	✅	✅
	Pause	✅	✅	✅	✅	✅	✅
	Remove	✅	✅	✅	❌	✅	✅
	Update budget	✅	✅	✅	✅	✅	✅
	Update bidding strategy	✅	✅	✅	❌	❌	❌
	Update dates	✅	❌	✅	✅	✅	✅
	Update name	✅	✅	✅	✅	✅	✅
	Update network settings	✅	❌	❌	❌	❌	❌
	Update EU political advertising	✅	❌	❌	❌	❌	❌
	Add label	✅	✅	❌	✅	✅	❌
	Remove label	✅	✅	❌	✅	✅	❌
Ad group	Create	✅	✅	✅	✅	❌	❌
	Enable	✅	✅	✅	✅	✅	✅
	Pause	✅	✅	✅	✅	✅	✅
	Remove	✅	✅	✅	✅	✅	✅
	Duplicate	❌	❌	❌	❌	✅	❌
	Update bid	✅	✅	✅	✅	✅	❌
	Update budget	❌	❌	❌	❌	✅	❌
	Update name	✅	✅	✅	❌	✅	✅
	Update target CPA	✅	❌	❌	❌	❌	❌
	Update target ROAS	✅	❌	❌	❌	❌	❌
	Update network settings	❌	✅	❌	❌	❌	❌
	Update demographics	❌	❌	❌	❌	✅	❌
	Update geo targeting	❌	❌	❌	❌	✅	❌
	Attach audience	❌	❌	❌	❌	✅	❌
	Detach audience	❌	❌	❌	❌	✅	❌
	Add label	✅	✅	❌	✅	❌	❌
	Remove label	✅	✅	❌	✅	❌	❌
Ad	Create	✅	✅	✅	✅	❌	❌
	Enable	✅	✅	✅	✅	✅	✅
	Pause	✅	✅	✅	✅	✅	✅
	Remove	✅	✅	✅	❌	✅	✅
	Duplicate	❌	❌	❌	❌	✅	❌
	Update	✅	✅	❌	❌	❌	❌
	Add label	✅	✅	❌	❌	❌	❌
	Remove label	✅	✅	❌	❌	❌	❌
Keyword	Create	✅	✅	✅	✅	❌	❌
	Enable	✅	✅	✅	✅	❌	❌
	Pause	✅	✅	✅	✅	❌	❌
	Remove	✅	✅	✅	❌	❌	❌
	Update bid	✅	✅	✅	✅	❌	❌
	Update final URL	✅	❌	❌	❌	❌	❌
	Add label	✅	✅	❌	✅	❌	❌
	Remove label	✅	✅	❌	✅	❌	❌
Negative keyword	Create	✅	✅	✅	✅	❌	❌
	Remove	✅	✅	✅	✅	❌	❌
Asset group	Enable	✅	✅	❌	❌	❌	❌
	Pause	✅	✅	❌	❌	❌	❌
	Remove	✅	✅	❌	❌	❌	❌
	Update name	✅	✅	❌	❌	❌	❌
Campaign criterion	Create	✅	✅	❌	❌	❌	❌
	Remove	✅	✅	❌	❌	❌	❌
Shared budget	Update budget	✅	✅	❌	❌	❌	❌
Product group	Update bid	✅	❌	❌	❌	❌	❌
Bid modifier	Set	✅	❌	❌	❌	❌	❌
	Remove	✅	❌	❌	❌	❌	❌
Recommendation	Apply	✅	❌	❌	❌	❌	❌
	Dismiss	✅	❌	❌	❌	❌	❌
Product target	Enable	❌	❌	✅	❌	❌	❌
	Pause	❌	❌	✅	❌	❌	❌
	Remove	❌	❌	✅	❌	❌	❌

If a request combines a platform, entity, and action that aren't supported together, the request is invalid, and not just unsupported by Optmyzr. If these actions are created, they will be refused.

No AI assistant, MCP call, or automation can apply a change directly to your account. Every change request must be reviewed and applied by a person on your team with Apply access.

Change Requests - User Guide