1
Target
Identify the entity
The destination never depends on the reviewer remembering it.
- Account
- Cardex US
- Campaign
- Prospecting CBO
- Entity ID
- 2384…0912
Approval workflow
Review every Meta Ads change before it reaches the account
Adrails treats approval as part of the data model, not a confirmation dialog added at the end. A proposed action contains the target, current value, new value, rationale and approval state.
Reviewed Sep 22, 2026
Product view
Review the exact campaign context before acting
Open the affected campaign, verify its settings and performance, then make the approval decision with the source context still visible.
Product workflow
Review the target, difference and evidence
Approval is a sequence of explicit checks around one concrete account mutation, not a generic confirmation step.
2
Difference
Compare exact values
The proposed mutation is legible before approval.
- Field
- Daily budget
- Current
- $420
- Proposed
- $500
3
Evidence
Check the reason
The reviewer sees which performance window supports it.
- ROAS
- 2.83
- CPA
- $31.40
- Window
- Last 7 days
4
Decision
Record the outcome
Approval, rejection and reviewer stay in the history.
- Status
- Pending
- Reviewer
- Thomas
- Published
- No
Illustrative workspace data. Values show the product flow and are not customer results.
FAQ
Common questions
Can approvals happen per proposed change?
Yes. Actions are reviewed at the entity and field level instead of accepting an entire queue blindly.
Does Adrails keep rejected proposals?
The workspace retains the decision context so the team can distinguish proposed work from approved work.
Next
Related resources
An AI agent for Meta Ads that waits for your approvalAI agent for Meta AdsAutomate Meta Ads work without automating away controlMeta Ads automationBuild complete Meta campaigns from one working briefCampaign builderManage multiple Meta ad accounts from one operating workspaceMulti-account operations