Blog
Field notes on Meta Ads automation.
The AdOps blog publishes 6 field notes on Meta Ads automation, written by the people who build and run the AdOps rule engine. Every post sits in one of four categories — playbooks, engineering, benchmarks and product — and every claim in them carries the number it rests on.
Rules that survived contact with a real ad account, the engineering behind them, and the numbers we check before publishing any of it.
Sample data Posts from 2026
-
Custom metrics that read your spreadsheet
A custom metric binds a Google Sheet column to a rule condition, so AdOps can act on margin, stock or a target you maintain by hand. How to lay the sheet out, where the value can be used, and how fresh it really is.
Product -
Dayparting rules for Indonesian Meta advertisers
Two AdOps metrics gate a rule on the clock and the day of the week. How the inclusive hour boundary works, when to use the timetable instead, and how to write a night budget reset that only fires once.
Playbooks -
ROAS targets that survive contact with reality
A ROAS target is arithmetic from your own margin, not a number copied from a benchmark table. How to derive it, which ROAS field AdOps is actually showing you, and how to keep the number in one place.
Benchmarks -
When to pause a Meta campaign, and when to wait
Pause rules fail because they fire on partial windows and leave no trace. A window with spend behind it, a tag on the name, and a way back — the three parts of a pause rule that survives.
Playbooks -
Writing your first AdOps automation rule
A step-by-step build of one working Meta Ads rule in AdOps — accounts, filters, a condition, an action, a schedule — and how to read its first execution log.
Playbooks
Every post ends the same way: go write the rule.
Start from a shipped template, point it at one ad account, and leave it in draft until the execution log looks right. Nothing runs on your campaigns until you set it live.
