Quickstart — your first rule

This quickstart takes you from a new AdOps account to one live rule in eight steps: confirm your email, complete company setup, connect Meta Ads, sync and activate an ad account, create a rule, add one task, choose a schedule, and press Set Live. Budget about fifteen minutes.

Before you start#

You need a Meta account with access to at least one ad account, and an email address you can read. AdOps enforces a password of 8 to 128 characters containing an uppercase letter, a lowercase letter, a digit and a special character at signup.

Step 1 — Confirm your email and finish onboarding#

Confirming the signup email is what starts the 14-day trial, so do it before anything else. AdOps then walks you through company setup and platform connection. Both screens are part of a forced sequence: you cannot reach the dashboard until they are done or explicitly skipped.

Step 2 — Activate the ad accounts AdOps may touch#

Sync pulls your ad accounts from Meta and inserts each one as Inactive. Nothing downstream reads an inactive account — not spend, not the dashboard, not a rule. Switching an account on is the consent step, and it is the cleanest way to bound what automation can reach while you are learning the product.

A resync is safe. AdOps records which accounts were active, inserts only accounts it has not seen before, and restores the active flags afterwards.

Step 3 — Build one small rule#

Resist the urge to encode your whole playbook in the first rule. A good first rule is one task, two conditions, and an action that is easy to undo.

{
  "action": "notify",
  "action_frequency": "1_days",
  "condition": {
    "operator": "AND",
    "conditions": [
      { "metric_key": "spend", "period": "today", "operator": "GREATER_THAN", "value": "500000", "compare": "value" },
      { "metric_key": "purchase_roas.omni_purchase", "period": "today", "operator": "LESS_THAN", "value": "2", "compare": "value" }
    ]
  }
}

That is the shipped Performance Monitor template: it fires on campaigns that have spent more than Rp 500,000 today while Purchase ROAS sits under 2, at most once a day. Importing a template is two clicks — press Templates in the Tasks & Conditions toolbar, Preview, then Import. The modal footnote is accurate: values are defaults, and you can edit them after importing.

Step 4 — Choose how often it runs#

Two modes, and only two. Run every <interval> takes one of ten fixed intervals from 15 minutes to 72 hours. Run on spesific days and time gives you a grid of 24 hour-rows across Su to Sa, plus a Week column that toggles an hour on all seven days at once. If a rule has no interval set, AdOps falls back to 60 minutes.

You can also tick Run within a date range to time-box the rule; the picker defaults to today through today plus 7 days.

Step 5 — Verify from the log, not from Ads Manager#

After the first run, open the rule’s three-dot menu and choose Logs. Each row is one execution batch with its Execution Time, Ad Account, Applied Items and Affected Tasks. Click into a batch and you get, per campaign and per task, an Executed / Not Executed / Skipped badge, the action’s parameters, every condition’s Pass or Fail with the actual value the engine saw, and a Before → After block when something changed.

That log is the fastest way to confirm the rule does what you meant, and it is where you should look first when it does not.

What to do next#

Read Anatomy of a rule before you write your second rule, then Scheduling a rule if you need dayparting.