Features
Everything AdOps can watch, and everything it can do.
AdOps is a rule engine for Meta Ads. Its features fall into four groups: automate writes and runs the rules, measure supplies the 45 metrics and 11 reporting periods those rules read, decide drafts a rule from a plain-language description, and operate schedules each run and logs what it changed.
Each feature below is a part of the product you can open, not a promise. The counts are taken from the software itself.
The vocabulary
Four numbers define what a rule can say.
A condition picks one metric and one reporting period. A task picks one action and, for five of the eleven, one cooldown. Everything else is arithmetic.
45
Meta Ads metrics an AdOps rule condition can test, across 6 categories
11
reporting periods selectable per condition, from Today to Lifetime
11
actions the AdOps engine executes on a campaign, from pause to set budget
11
action-frequency cooldowns, from 15 minutes to once in a lifetime, accepted by 5 of the 11 actions
Automate
How does AdOps change a campaign without you?
The rule engine itself: the conditions that decide, the actions that execute, and the pre-filters that keep a rule pointed at the campaigns you meant.
Sample data -
Rule automation
Conditions on live Meta metrics paired with actions the engine executes on your campaigns, with an execution log behind every run.
Learn more -
Automation actions
Eleven executable actions across lifecycle, budget and naming, each with its own parameters and an optional cooldown.
Learn more
Measure
What numbers can a rule read?
The metric catalogue a condition draws on, the spreadsheet-backed figures you maintain yourself, and the dashboard that reports the same numbers back.
Sample data -
Metrics library
Forty-five Meta Ads metrics in six categories, eleven reporting periods per condition, and metric-versus-metric comparison.
Learn more -
Custom metrics
A named metric bound to a Google Sheet, resolved at evaluation time, usable in conditions, budget values and campaign names.
Learn more -
ROAS dashboard
Two ROAS cards, a monthly budget meter, a spend breakdown, a campaign leaderboard and an account comparison across four periods.
Learn more
Decide
What helps you choose which rule to write?
Drafting help for the rule you have in mind, returned as editable JSON with a confidence score rather than an action already taken.
Sample data Operate
What happens once a rule is live?
When each rule becomes due, what the engine did on every campaign it touched, and the evidence row it left behind either way.
Sample data -
Scheduling and dayparting
A check interval or a weekly timetable decides when a rule runs; time conditions decide which hours and weekdays it may act on.
Learn more -
Execution logs
Batch records, per-campaign per-task results, condition-level pass and fail evidence, and before and after values for every change.
Learn more
Point one rule at one ad account.
Start from a template, leave it in draft until the estimated match looks right, and set it live when you are ready. Nothing runs on your campaigns until you say so.