Language
Contact us

Documentation

AdOps documentation

The AdOps documentation explains how to connect a Meta ad account, write a rule from conditions and actions, schedule it, and read the execution log afterwards. It runs to 14 pages across 6 sections, from the quickstart through the metrics and actions references to a checklist for a rule that never fired.

Written from the product as it behaves today. Where the engine has a limit, the page says so.

Start on the left. The sidebar carries every page in the manual, grouped the way the product groups the work: get connected, write a rule, understand the metrics behind it, then read what the engine actually did.

Every page states what the field is called in the interface, what the engine stores, and what it does not do. Nothing here describes a feature that is not shipped.

Start here

The two pages to read first.

One explains what AdOps is. The other takes you from a confirmed email to a rule that is live on a real ad account.

The full manual

Browse by section.

Each section stands on its own — a reference you can open at the page you need rather than read front to back.

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. Sample data
Every rule, what it manages and when it last fired. The toggle is the only thing between draft and live. Read the details

How this is published

Every page is also a plain Markdown file.

AI crawlers do not execute JavaScript, and they should not have to parse a navigation bar to find a sentence.

Append .md to any documentation URL and you get the same page as Markdown — the article, its key facts and its steps, with the canonical URL and the last-updated date at the top and no layout chrome at all. Every mirror is indexed in llms.txt at the site root.

llms.txt

This documentation set

Pages
14
Sections
6
Languages
English and Bahasa Indonesia
Most recent update
20 August 2026
Markdown mirror
Every page append .md to the URL

The manual is short. The first rule is shorter.

Read the quickstart, copy one of the 10 shipped templates, point it at a single ad account, and leave it in draft until the numbers look right.

Start free trial Learn more

14 days free · no card required

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