Glossary

How a Meta Ads account is built.

6 terms Updated 20 August 2026

Structure terms name the objects an AdOps rule points at: the ad account that holds the spend, the campaign that carries the objective and the budget, the ad set beneath it, and the daily or lifetime budget each one runs on. AdOps writes at campaign level, so these are the objects a rule can change.

Knowing which object holds the budget is what decides where a rule can usefully act.

Every structure term, alphabetically

Ad account
An ad account is the billing and permissions container in Meta Ads: it holds one currency, one payment method, an account ID prefixed with act_, and every campaign run under it.
Ad set
An ad set is the level of a Meta Ads campaign that holds targeting, placements, optimisation and schedule settings, and its own daily or lifetime budget unless the campaign holds the budget instead; it contains one or more ads.
Campaign
A campaign is the top level of the Meta Ads account structure: it holds the advertising objective and, when campaign budget optimization is on, the budget, and it contains one or more ad sets.
Campaign budget optimization CBO
Campaign budget optimization (CBO) is a Meta Ads setting that places a single budget on the campaign instead of on each ad set, letting Meta distribute spend across the ad sets it expects to perform best.
Daily budget
A daily budget is the average amount a Meta Ads campaign or ad set is allowed to spend per day; Meta may spend more on a high-opportunity day and less on a quiet one, averaging out to the set figure over the week.
Lifetime budget
A lifetime budget is the total amount a Meta Ads campaign or ad set may spend across its entire schedule, rather than a per-day amount, with Meta pacing the spend across the scheduled dates.
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. Sample data
Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators. Read the details

Knowing the term is step one. Writing the rule is step two.

Every metric on this page is selectable in the AdOps rule builder, paired with a reporting period and compared against a number you choose. Start from a template and leave it in draft until the figures look right.

Contact us See pricing

14-day trial · no card

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