a.ads
← All guides

Proposals and the Approval Center

Where proposals come from, how to read the evidence, and what approving actually does.

Where proposals come from

Two sources feed your queue:

  • The nightly engine. A deterministic engine reviews every selected ad account each night and proposes changes backed by your real performance data: pausing fatigued or wasteful ads, scaling ad sets that have earned it, refreshing tired creative. It's deliberately conservative — a handful of proposals per account at most, and a dismissed proposal won't come back for 14 days.
  • The agent and you. Campaign drafts you build in the wizard, and changes the AI agent drafts in chat, land in the same queue.

Nothing in the queue has touched your ad account. A proposal is a suggestion until you act on it.

Reading a proposal card

Each card shows what the change is, the reason, the expected impact, and a risk level. Proposals from the nightly engine carry their evidence inline — a small trend chart of the exact metric series that justified the suggestion. You're never asked to approve on trust.

Approve or dismiss
  1. Open the Approval Center from the rail.
  2. Review the card and its evidence.
  3. Approve to accept, or dismiss with an optional reason. Reasons are remembered and the engine respects the cooldown.
What approval actually does

Approving hands the action to our executor — the single, gated component allowed to write to ad platforms, and only for actions in the approved state.

  • Pauses and budget changes are applied directly to Meta. A pause is always reversible — you can resume from the product or in Ads Manager.
  • Campaign publishes create the full campaign on Meta in a paused state. It will not spend a cent until you take it live, which itself goes back through the Approval Center as a go-live request.

Every state transition — proposed, approved, executed, dismissed — is written to an append-only audit trail.

Questions? hello@dotstack.io