Overview
Meta Ads Copilot is read-only by default. It can pull any report, analyze any data, and generate recommendations without asking. But it will never take action without explicit approval. This safety model protects you from unintended spend changes while enabling fast, autonomous reporting.The Core Principle
Always ask before acting. Any operation that affects ad delivery or spend requires your explicit confirmation:- Pausing or resuming ads, adsets, or campaigns
- Changing budgets (daily or lifetime)
- Modifying bids or optimization goals
- Creating or deleting campaigns
Read-Only Operations (No Approval Needed)
The copilot can run these autonomously:1
Pull insights and reports
2
Analyze performance data
- Calculate efficiency metrics (CPA, ROAS, CPC)
- Identify trends (CTR declining, frequency climbing)
- Compare against benchmarks
- Flag bleeders and winners
3
Generate recommendations
- “Pause this bleeder — CTR 0.4%, spend $127”
- “Shift $100/day from Retargeting to Product Launch”
- “Resume this winner — previously 3.2% CTR, $18 CPA”
4
Log findings to learnings.md
Append insights and patterns to
workspace/brand/learnings.md for future context.Reports and analysis are always safe. The copilot can explore data freely without risk.
Approval-Required Operations
These actions require explicit user confirmation:Pause/Resume Actions
Budget Changes
Campaign/Ad Creation
Approval Workflow
Here’s how the always-ask-before-acting principle works in practice:1
Agent identifies action opportunity
From reports or user request, the copilot determines an action is needed.Example:
2
Agent presents recommendation with data
3
Agent requests explicit approval
4
User approves or rejects
You respond:
"yes"or"proceed"or"do it"→ Action executes"no"or"skip"or"not now"→ Action skipped- Ask for more info → Agent provides additional context
5
Agent executes and logs
On approval:Then logs to
workspace/brand/learnings.md:Batch Approvals
When multiple actions are recommended, you can approve all at once:Audit Trail
Every action is logged toworkspace/brand/learnings.md with:
- Timestamp — When the action occurred
- What changed — Ad ID, name, old/new values
- Why — Data justification (metrics, thresholds)
- Who approved — User confirmation method
Example Log Entry
This audit trail provides full transparency and accountability for every action taken.
Preventing Accidents
Confirmation Requirements
The copilot recognizes these as approval:"yes""proceed""do it""confirm""go ahead"
Double-Check for High-Risk Actions
For particularly risky actions (e.g., pausing an entire campaign), the copilot may ask twice:Undo Warning
If you accidentally approve an action:- Pause/Resume: Immediately reverse by resuming/pausing
- Budget change: Set budget back to previous value (check learnings.md for old value)
- Campaign creation: Pause the new campaign immediately
Customizing Safety Settings
You can configure approval requirements inad-config.json:
Daily Workflow with Safety Model
Here’s how the safety model enables efficient, safe ad management:Morning Routine (Automated)
Action Phase (Approval Required)
Reallocation (Approval Required)
Next Steps
- Pause and Resume — Stop bleeders, restart winners with approval
- Budget Optimization — Shift budget safely with data-backed recommendations