Structure

Ad account

Updated 20 August 2026

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.

Key facts about Ad account

Also known as
Advertising account, Meta ad account
Category
Structure
Last updated
20 August 2026

In AdOps

How does Ad account work inside AdOps?

AdOps syncs ad accounts from Meta and inserts every one of them inactive, so nothing is touched until a person switches it on. A rule can attach up to 5 ad accounts, and the engine queues one job per ad account so a slow account never blocks the rest.

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

An ad account is the container Meta bills against: one currency, one payment method, one account ID, and every campaign beneath it. AdOps treats the ad account as its unit of blast radius. Accounts pulled from Meta arrive switched off, and only the ones a person activates are read, reported on or acted upon.

How does AdOps limit what it can touch?

Every ad account discovered during a sync is inserted inactive. Activation is an explicit per-account switch on the Ad Accounts screen, and that flag is what scopes everything downstream: spend refresh, the Purchase ROAS and Aggregated ROAS cards, the spend breakdown and the account comparison all read active accounts only.

How many ad accounts can one rule cover?

Up to 5. The rule builder’s Ad Accounts field reads ‘Select up to 5 ad accounts you want to manage’, and an agency running the same logic across clients attaches several accounts to one rule rather than duplicating the rule per client.

What happens per ad account when a rule runs?

The engine fetches each account’s entities separately and enqueues one job per ad account, so the accounts are processed independently. Entity fetches are retried up to 3 attempts, waiting 1 second then 2 seconds. If an account still fails, it is skipped and the remaining accounts continue.

Glossary

The terms an advertiser usually reads in the same sitting.

Turn this metric into a rule that watches it.

Pick the metric, pick one of the 11 reporting periods, set the threshold, and choose what happens when it is crossed. Nothing runs on your campaigns until you set the rule live.

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