# Quickstart — your first rule

> Sign up, connect Meta, activate an ad account and set your first rule live in eight steps.

Source: https://adops.id/docs/quickstart/
Last updated: 2026-08-20
Publisher: AdOps (https://adops.id) — an independent product, not affiliated with Meta Platforms, Inc.

---

## Key facts

- **Steps from signup to a live rule:** 8
- **Ad accounts you can attach to one rule:** up to 5 (the builder hint reads "Select up to 5 ad accounts you want to manage")
- **Fastest check interval:** 15 minutes (the interval list runs 15 minutes to 4320 minutes (72 hours), 10 options)
- **New ad accounts after a sync:** inactive by default (AdOps reads and writes only accounts you switch on)

## Steps

1. **Confirm your signup email** — After you sign up, AdOps sends a confirmation email. Click the link on the Confirm your email address screen. Confirming starts the 14-day trial. The Resend Confirmation Email button has a 60-second cooldown and shows "Resend available in <n>s" while it counts down.
2. **Complete company setup** — On the Tell us about your company screen, enter a Company Name of at least 3 characters, pick a Company Industry (Agency, Services, E-commerce or Other) and a Monthly Ad Budget band from Below Rp 100 million to Above Rp 3B, then press Continue.
3. **Connect Meta Ads** — On the Connect ad platform screen choose Meta Ads. TikTok Ads, Google Ads and Snapchat Ads are shown with a Coming Soon badge and cannot be selected. AdOps verifies the token against the Meta Graph API and shows Connected on the Meta Ads card in Integrations.
4. **Sync your ad accounts** — Open Integrations, then Ad Accounts, and press Sync. AdOps walks /me/adaccounts 100 accounts per page and inserts every account it finds as Inactive.
5. **Activate the accounts you want automated** — On the Ad Accounts page, switch on the toggle for each account AdOps may touch, or select several rows and use Activate in the bulk bar. Only active accounts are read for spend, dashboards and rules.
6. **Create a rule and scope it** — Go to Rule List and press "+ Create rule". Name the rule, attach up to 5 ad accounts, then in Filter Configuration pick the level (Campaigns or Ad sets) and add filters on Campaign ID, Campaign Name or Campaign Status. Watch the "Estimated match: N Campaigns" readout to see the blast radius before you save.
7. **Add a task** — In Tasks & Conditions press Add Task, choose an action from the General, Budget or Name/Text groups, then add conditions with the metric, period, operator and value pickers. Set the task's AND/OR pill and, for Notify, Duplicate or the three budget actions, an action frequency.
8. **Set the schedule and go live** — In Schedule Configuration choose "Run every <interval>" (15 minutes to 72 hours) or "Run on spesific days and time" and click the hours on the Week/Su-Sa grid. Press Set Live. Open the rule's Logs after the first run to confirm what it did.

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.

```json
{
  "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](/docs/anatomy-of-a-rule/) before you write your second rule, then [Scheduling a rule](/docs/scheduling-a-rule/) if you need dayparting.