AI agents in AdOps: decide what they can change before they act

A daily campaign report flags three delivery problems. An AI assistant can summarize them in seconds. An AI agent may also be able to change budgets, pause ads, or send instructions to another system. That extra ability changes the operating question: who approved the action, and how will the team know what happened?

Agentic advertising is moving into formal industry work. IAB Tech Lab’s AAMP initiative, updated in September 2026, covers AI agents working with advertising standards and workflows. Google also announced agentic capabilities for Ads and Analytics in August 2026. Those developments make access and change control practical AdOps concerns.

Separate the jobs before granting access

Start with the actual task. “Help manage campaigns” is too broad to define what success or a mistake looks like.

A useful first assignment is narrower: review completed-day delivery, identify campaigns below plan, and prepare a proposed change with supporting numbers. The output should name the campaign, the reporting cutoff, the current setting, the proposed setting, and the reason.

Consider three levels of access:

Job	What the system can do	What the operator checks
Investigate	Read approved reports and settings	Source, date range, and calculation
Prepare	Create a draft change or ticket	Exact values and affected campaigns
Execute	Apply an allowed change	Limits, approval, result, and rollback

These are suggested operating levels, not a universal industry certification. A tool that performs well at the first level has not automatically earned the third.

Test a proposal with real constraints

Suppose a campaign needs an average of $900 per day to finish its approved budget, but an explicit daily cap is $750. The agent recommends raising the cap to $950.

The recommendation is incomplete until it checks the remaining budget, end date, shared limits, and reason for the existing cap. It also needs to distinguish a setting error from a deliberate business decision. A cap may have been imposed while a landing-page problem was being investigated.

Require the proposal to include:

• The report and settings used, with their retrieval times.
• The calculation supporting the recommendation.
• The approved campaign constraints.
• Any missing information that could change the recommendation.
• The person or rule authorized to approve the action.

The campaign pacing calculator can help check the arithmetic. It cannot decide whether more spend meets the campaign brief.

Make an executed change traceable

If execution is allowed, use the narrowest permissions that support the job. Limit the accounts, campaigns, settings, and values the agent can change. Put meaningful limits in the system that accepts the change, rather than relying only on a sentence in a prompt.

Keep an action record with the previous value, requested value, actual saved value, timestamp, approval reference, and outcome. Read the setting back after applying it. A successful request does not by itself prove the intended setting is active.

Plan for retries. If a request times out after a budget increase, the next attempt should check what happened before applying another increase. Prefer setting an approved absolute value over repeatedly adding a percentage.

Test the uncomfortable cases

A clean demonstration rarely includes yesterday’s report labeled as today’s, two campaigns with similar names, or a last-minute manual edit. Your trial should.

Use copies or a controlled environment to test stale data, missing permissions, conflicting instructions, partial failures, and an operator changing the same setting. Check whether the agent stops when it cannot identify the right campaign or confirm the current value.

Treat text inside reports, creative files, and external pages as material to inspect. It should not become an instruction to change access or send data elsewhere.

Start with one workflow you can evaluate

For a two-week trial, choose one repeated task and compare assisted work with the existing process. Track incorrect proposals, accepted proposals, operator corrections, time saved, and changes that needed reversal.

Expand access only when the evidence supports it. The campaign owner should still be able to answer a simple question: what changed, why, and who was responsible?