Skip to main content
Guardrails define hard workspace policy. Autonomy defines how new work starts and whether an accepted launch pauses for review. Provider permissions and ad-account state still apply underneath both.
Guardrails reduce risk; they do not validate the campaign, creative, destination, audience, tracking, or provider account. Keep a human review step until real outputs and recovery paths are proven.

Set performance targets

Open Settings → Guardrails. Targets are decision thresholds, not promises. Align their date range, conversion definition, and attribution source with how the team evaluates performance. Blank numeric fields use Marketer’s system defaults. If a number is important to your operating policy, enter it explicitly rather than relying on an unseen fallback.

Set currency-bound spend caps

Choose the guardrail currency first, then set:
  • Monthly cap;
  • Daily cap; and
  • Minimum spend floor.
Caps are enforced only on ad accounts billed in the selected currency. Marketer does not convert a different provider currency to make it fit the cap.
A USD cap does not govern an account billed in EUR, GBP, or another currency. Verify each connected ad account’s native billing currency before relying on a cap.
The minimum spend floor expresses an operating lower bound; it does not override a provider rejection, a hard cap, a paused campaign, or unavailable funds.

Control scaling

Use all three together. For example, a maximum can bound the size of an allowed increase while the approval threshold sends a smaller high-risk band to a reviewer.

Protect campaigns

Use Untouchable campaigns to select synced Meta campaigns the agent must never modify.
  • Select by the exact Meta campaign and account.
  • Revisit the list when campaigns are renamed, replaced, or archived.
  • Keep legal, evergreen, or externally managed campaigns protected.
  • Confirm a protected campaign remains selected after a provider reconnection or roster change.
Untouchable status protects modification. It does not remove the campaign from read-only analysis.

Configure new-customer acquisition

New customer acquisition is configured per Meta ad account. Choose the Custom Audiences that represent known customers under Customer exclusions. This setting uses provider audiences to prevent acquisition work from targeting existing customers. It is separate from:
  • Existing customers reporting roles;
  • Engaged audience reporting roles; and
  • ad-set-specific targeting choices.
Build and verify audiences in Custom audiences, then confirm the exclusion on the exact Meta ad account.

Configure autonomy

Open Settings → Autonomy.

Default creation mode

This is a workspace default, not a lock. A teammate can choose another mode on an individual brief.

Autonomy level

The advanced control can appear as Launch accepted orders live (ACTIVE). Turning it on opens Go hands-off? or Launch accepted orders live? and states the spend consequence. Hands-off is available only on managed plans. Guardrails and spend caps remain active, but the paused review stop is removed.
1

Validate read-only outputs

Compare real analysis with connected provider data and completed coverage.
2

Enter explicit limits

Set currency, spend caps, scaling controls, customer exclusions, and untouchable campaigns.
3

Keep Review everything

Test proposals and accepted launches while they remain paused.
4

Inspect a real paused launch

Verify provider account, destination, tracking, creative, audience, budget, naming, and approval ownership.
5

Expand one workflow

Consider Hands-off only for a proven scope with monitoring and a named rollback owner.

Change review checklist

  • Active workspace and effective role
  • Ad account and native currency
  • Target and break-even definitions
  • Daily and monthly caps
  • Increase master switch, maximum, and approval threshold
  • Untouchable campaign roster
  • Customer-exclusion audiences
  • Default brief mode
  • Review everything or Hands-off consequence
  • Notification owner for performance, budget, and approval events

Recovery

  • If a change is blocked, identify whether the blocker is role, provider permission, guardrail, approval, account state, or sync coverage.
  • If hands-off was enabled unintentionally, return to Review everything before starting more work.
  • If the wrong currency was configured, correct the guardrail and audit affected account coverage; do not assume conversion applied.
  • If an audience exclusion is missing, pause acquisition work until the correct Meta account and audience are selected.
  • If a protected campaign changed, contain provider-side activity and review whether it was protected at the time and in the correct workspace.

Next step

Configure Notifications and billing so warnings, approvals, and failed-payment events have a responsible recipient.
Last modified on August 9, 2026