Use cases

Meta Ads automation playbooks, by advertiser type

AdOps publishes a playbook for each kind of Meta advertiser: e-commerce scaling, lead generation, agency multi-account work, dayparting and budget protection. Every playbook states the situation it fixes, then lists the actual rules — conditions, reporting periods and actions — that a team in that situation writes inside AdOps.

No case studies and no unnamed customers. Each page is a set of rules, printed the way the rule builder prints them, with the reasoning behind every threshold.

Playbooks

Which playbook matches your account?

Each one names the advertiser it was written for, so start with the description that sounds like your week.

The AdOps Task Templates modal showing six starting points — Scale Profitable Campaigns, Pause Unprofitable Campaigns, Tiered Budget Scaling, Night Budget Reset, Tag Campaign Performance and Pause plus Tag Failed — each with a priority badge and Preview and Import buttons. Sample data
Ten ready-made tasks to start from. Preview one before importing; everything it sets is editable afterwards. Read the details

Anatomy

What is inside every playbook?

The same three parts, in the same order, on every page in this section.

The situation, stated plainly
Each playbook opens with the problem it addresses and the outcome once the rules are running, both written as things that happen in an ad account rather than as benefits.
Rules you can copy
Every rule is printed the way the builder shows it — metric, reporting period, operator, value, then the action that fires — so it can be rebuilt in AdOps without translation.
Why each rule is shaped that way
Each rule carries the reasoning behind its thresholds and its check frequency, so you can move the numbers to fit your account without breaking the logic.

Start from a playbook, not a blank rule.

Copy the rules from the playbook closest to your account, point them at one ad account, and leave them in draft until the numbers look right.

Contact us See pricing

14 days free · no card required · billed in Rupiah

Inside the product

What the screens actually look like

Nine screens from the working dashboard — the rule builder, the metric picker, the dayparting grid and the log that records what happened. Scroll the strip.

  • The AdOps Performance Dashboard showing a Purchase ROAS card at 2.380x and an Aggregated ROAS card at 2.088x, both badged Profitable, a Monthly Budget card at Rp 155jt, and a Spend Breakdown ranking the top five ad accounts against a budget utilisation bar at 45.5 per cent.
    Performance Dashboard. Two ROAS figures to three decimals, a budget meter, and spend ranked by ad account — over Today, Last 7 days, Last 30 days or This month.
  • The AdOps rule list showing twelve automation rules, each with an on/off toggle, the ad accounts it manages, and when it last triggered — some minutes ago, others on a dated timestamp.
    Rule List. Every rule, what it manages and when it last fired. The toggle is the only thing between draft and live.
  • The AdOps condition builder showing a task with time-of-day conditions across seven day tags, a nested AND group holding a lifetime spend condition under 400,000, and a second task with four stacked metric conditions.
    Conditions. Metric, period, operator, value — joined with AND or OR, and nestable, so a rule can say something a dropdown cannot.
  • The AdOps metric picker open over a condition row: a panel with Meta Ads and Custom metrics tabs, a search box, and a scrolling list of metrics with Spend selected.
    Metric picker. Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators.
  • The AdOps dayparting timetable: a grid of hours against the seven days of the week, with the daytime hours filled navy for every day and the night hours and weekend evenings left empty.
    Dayparting grid. Or draw the hours instead. Anything outside the shape you fill in simply does not run.
  • An AdOps execution log detail: one campaign, two action panels badged Not Executed, each listing the action parameters and every condition evaluated with its actual value, its expected value and a Pass or Fail badge.
    Rule Log detail. Why a rule did nothing is recorded as carefully as why it did something — actual against expected, condition by condition.
  • The AdOps activity log listing budget increases and campaign renames, each row naming the affected campaign by id, the rule that caused it and how long ago it happened.
    Activity Log. One row per change AdOps made in your account, naming the campaign and the rule responsible.
  • The AdOps ad account list: eighteen Meta ad accounts with on/off toggles, account ids, Active or Inactive badges and this month’s spend in rupiah.
    Ad Accounts. Accounts discovered from Meta arrive switched off. Nothing is read, and nothing is changed, until you turn one on.
  • The AdOps custom metric editor mapping a Google Spreadsheet: a spreadsheet id, a sheet name, a column to match campaigns on and a column holding the values.
    Custom metric. Point AdOps at a sheet, name the matching column and the value column, and your own number joins the metric list.

Every figure is rebuilt from the product’s own interface and filled with invented data — no customer name, ad account or spend figure appears anywhere on this site. See how a run works