Overview

Moby Automations can help you monitor ad performance on a schedule and propose or make supported changes based on rules you define.

This article shows how to set up an Automation that reviews performance, applies guardrails, and prepares ad account actions with reasoning attached.

Before you begin

You need:

Moby 2 Automations
Connected ad platform accounts
Action access enabled for your account
A clear action approval behavior for your team
Performance rules your team is comfortable using

See Review and approve Moby Actions before creating an action Automation.

Steps

Write your rules in plain language.
1. Include the metric, threshold, read window, and action.
  Examples:
  - “Each morning, pause any ad with more than $100 spend over the last 7 completed days and ROAS under 1.0.”
  - “Scale ad set budgets 20% when 7-day ROAS is above 4.0. Cut budgets 20% when 7-day ROAS is below 2.5.”
  - “Before pausing an ad set, check whether one or two ads are dragging it down, and propose pausing those ads instead.”
Add guardrails.
1. Strong rules include:
  - Maximum budget change per day
  - Campaigns or ads Moby should never touch
  - Cooldowns so the same entity is not changed too often
  - Minimum spend thresholds
  - Confirmation windows, such as two consecutive days below target
  - A maximum number of proposed changes per run [VERIFY: confirm whether this is a product setting or instruction-level convention]
Choose how changes should be handled.
1. Moby Actions follow your account’s action approval behavior. Scheduled actions may run automatically or wait for review before execution. When approval is required, Moby prepares the proposed change and waits for review.
Set the cadence and destination.
1. Daily morning runs are common for ad monitoring. Pick a cadence that matches how often your team wants to review performance.
Run the kickoff.
1. Moby runs a kickoff so you can review the first evaluation before the Automation runs on schedule.
Review proposals and refine.
1. Each proposal should include the rule that matched and the evidence behind it. When an approval card appears, choose Approve, Reject, or No, and tell Moby what to do differently.

What a good proposal looks like

A useful proposal explains:

The entity Moby wants to change
The current state
The proposed change
The metric and date range used
The threshold that was crossed
The reason for the action

Example:

“Reduce this ad set’s daily budget from $100 to $80. Over the last 7 days, ROAS was 1.66 against a 2.5 floor. Reducing budget keeps the ad set live while limiting spend.”

If a proposal does not include enough evidence, reject it and tell Moby what context you need.

Tips

Start with review-only proposals before allowing faster execution.
Tell Moby to create new campaigns, ad sets, or ads in a paused state if you want to review them before spend begins.
Use exemption lists for launches, evergreen winners, seasonal pushes, or executive-priority campaigns.
Keep daily exposure in mind. Cap the number or size of changes one run can propose.
Moby can use action details, including prior and new values when available, to help restore supported changes if you ask it to reverse an action.

⚠️ Warning: Rules act on the data available at run time. Protect important launches and seasonal pushes with explicit exemptions rather than relying on thresholds alone.

Let an automation manage your ads with rules