# AdOps vs Meta Automated Rules

> Meta Automated Rules are the right default for advertisers who only need Meta's own metrics and a 30-minute check, while AdOps is worth adding when a rule has to read a Google Sheet, run every 15 minutes, or rewrite a campaign name.

Source: https://adops.id/compare/adops-vs-meta-automated-rules/
Last updated: 2026-08-20
Publisher: AdOps (https://adops.id) — an independent product, not affiliated with Meta Platforms, Inc.

---

## Key facts

- **AdOps shortest check interval:** 15 minutes (One of 10 interval options, the longest being 72 hours.)
- **Meta documented schedule types:** DAILY, HOURLY, SEMI_HOURLY, CUSTOM (SEMI_HOURLY runs every 30 minutes, per Meta's Marketing API scheduling guide.)
- **AdOps rule metrics:** 45 across 6 categories
- **AdOps executable actions:** 11 (Including three that rewrite campaign-name text.)
- **AdOps external data source:** Google Sheets (Spreadsheet id, sheet name, lookup column, value column.)
- **Platforms AdOps supports today:** Meta Ads only (TikTok Ads, Google Ads and Snapchat Ads are listed as coming soon.)

**Choose Meta Automated Rules when:** Choose Meta Automated Rules when every condition you need is already a Meta metric, a 30-minute check is fast enough, and you want bid changes or ad-level actions. They are built into Ads Manager, need no access token or third-party connection, and Meta's documented execution types include CHANGE_BID, REBALANCE_BUDGET and ROTATE, none of which AdOps implements.

**Choose AdOps when:** Choose AdOps when a rule needs to compare a live Meta metric against a number your team maintains in a Google Sheet, when a 15-minute check matters, when you want campaign names rewritten with live figures, or when you need a per-campaign execution log that shows the actual value against the expected value for every condition.

| Criterion | AdOps | Meta Automated Rules |
|---|---|---|
| Minimum check frequency | 10 fixed intervals from 15 minutes to 72 hours, or a 7-day by 24-hour timetable of 168 slots. | Meta's ad-rules API documents schedule types DAILY, HOURLY, SEMI_HOURLY (every 30 minutes) and CUSTOM. |
| Metric vocabulary | 45 rule metrics in 6 categories - conversion 16, cost efficiency 15, engagement 7, time-based 3, core performance 2, custom 2. | Meta's own delivery, cost and conversion metrics as exposed in the Ads Manager rule builder. |
| External data as a condition | A custom metric names a Google spreadsheet id, a sheet name, a lookup column and a value column, resolved at evaluation time. | No external data source is documented for automated rules; conditions use Meta's metrics. |
| Action catalogue | 11 actions - start, pause, delete, duplicate, increase, decrease and set budget, add, remove and replace campaign-name text, and notify. | The adrules_library reference documents execution types including PAUSE, UNPAUSE, CHANGE_BUDGET, CHANGE_CAMPAIGN_BUDGET, CHANGE_BID, REBALANCE_BUDGET, ROTATE and NOTIFICATION. |
| Bid changes | Not supported. AdOps has no bid action. | CHANGE_BID is a documented execution type. |
| Campaign renaming | Three name actions with TEXT, APPEND and OVERWRITE modes and tokens such as {date}, {time} and {metric|spend|today}. | No rename action appears in the documented execution-type list. |
| Levels | Rules evaluate at campaign or ad-set level, and every write path is campaign-shaped. | Rules can be applied to campaigns, ad sets and ads. |
| Condition logic | One condition group per rule, combined with AND or OR, using 6 comparison operators and 11 reporting periods per condition. | Multiple conditions on one rule, documented in the Meta Business Help Centre. |
| Anti-thrash cooldown | A per-action frequency with 11 values from 15 minutes to once in a lifetime, available on 5 of the 11 actions. | Not documented separately from the rule's own schedule. |
| Execution evidence | Per campaign and per task - an Executed, Not Executed or Skipped badge, actual against expected for every condition, before and after values, and the execution time in seconds. | Ads Manager provides a rules view for reviewing active rules and the changes they have made. |
| Natural-language rule drafting | Describe the goal in a sentence and AdOps returns draft tasks with a confidence score from 0 to 100 into the normal rule editor. | Not documented as part of the automated-rules builder. |
| Rule-outcome alerts | Not delivered. AdOps sends no Slack or email alert when a rule fires; results are read in the rule log. | NOTIFICATION is a documented execution type. |
| Setup and blast radius | Connect a Meta access token, then activate each ad account explicitly - a discovered account is inactive until switched on. | Nothing to connect. Rules live in the ad account you already administer. |
| Commercial fit | Indonesian product, invoiced in Rupiah through Duitku, with a 14-day trial that starts when the signup email is confirmed. | Built into Ads Manager, so there is no separate vendor relationship to manage. |

AdOps and Meta Automated Rules both run condition-and-action rules against Meta ad campaigns. Meta's version is built into Ads Manager and checks as often as every 30 minutes. AdOps is a separate Indonesian platform that checks as often as every 15 minutes, reads Google Sheets as a rule input, and rewrites campaign names.

## What do Meta Automated Rules do on their own?

Meta Automated Rules live inside Ads Manager and act on the campaigns, ad sets and ads in the account you already administer. As of August 2026, Meta's Marketing API reference for [adrules_library](https://developers.facebook.com/documentation/ads-commerce/marketing-api/reference/ad-account/adrules_library) documents execution types including PAUSE, UNPAUSE, CHANGE_BUDGET, CHANGE_CAMPAIGN_BUDGET, CHANGE_BID, REBALANCE_BUDGET, ROTATE and NOTIFICATION, and the [advanced scheduling guide](https://developers.facebook.com/docs/marketing-api/ad-rules/guides/advanced-scheduling) documents schedule types DAILY, HOURLY, SEMI_HOURLY and CUSTOM. SEMI_HOURLY runs a rule every 30 minutes.

That is a genuinely capable engine, and it is the one part of this comparison that needs no connection, no access token and no second vendor.

## Where does AdOps go further than Meta's built-in rules?

AdOps adds four things Meta's documentation does not describe for automated rules. First, an external data source: a custom metric names a Google spreadsheet id, a sheet name, a lookup column and a value column, so a condition can test a live Meta metric against a target ROAS, a margin or a stock level a human maintains in a sheet. Rows are cached in memory for 2 minutes with a MongoDB fallback.

Second, campaign-name writes. Three of the 11 AdOps actions add, remove or replace text in a campaign name, in TEXT, APPEND or OVERWRITE mode, and the text can carry tokens such as `{date}`, `{time}` and `{metric|spend|today}` that resolve to live values. That turns the Ads Manager campaign list into a readable scoreboard.

Third, a per-action cooldown. Each task inside a rule carries its own action frequency, one of 11 values from 15 minutes to once in a lifetime, on 5 of the 11 actions. A rule can therefore check every 15 minutes but only raise a given campaign's budget once every 2 hours.

Fourth, natural-language drafting. Describe the goal in a sentence and AdOps returns draft tasks with a confidence score from 0 to 100, written into the same rule editor a human edits, tagged as AI generated.

## How often does each one check a campaign?

AdOps offers 10 check intervals, from 15 minutes to 72 hours, or a weekly timetable of 7 days by 24 hours, which is 168 selectable slots. Meta's documented tightest schedule type is SEMI_HOURLY at every 30 minutes.

The dispatcher behind AdOps sweeps for due rules every 10 seconds and fans work out as one job per ad account, with entity fetches retried up to 3 total attempts, waiting 1 second then 2 seconds. That is dispatch latency, not a promise of instant action: a rule fires no more often than the interval its owner chose.

## What does each keep as evidence after a rule fires?

AdOps writes a batch record per run plus per-campaign, per-task results. The Rule Log Detail screen shows, for each campaign and each task, an Executed, Not Executed or Skipped badge, the action's parameters, the actual value against the expected value for every condition, before and after values where the action changed something, the execution time in seconds, and the next scheduled execution.

Ads Manager provides its own rules view for reviewing active rules and the changes they have made. The practical difference is granularity: AdOps records why a condition failed, with the number it saw, on a per-campaign basis.

## Where is AdOps behind Meta Automated Rules?

In four places, and they matter. AdOps has no bid action, so CHANGE_BID has no equivalent. AdOps evaluates at campaign and ad-set level but every write path is campaign-shaped, so there is no ad-level action parity. AdOps does not deliver rule alerts by Slack or email, while NOTIFICATION is a documented Meta execution type. And AdOps conditions form one group combined with AND or OR, not a nested logic tree.

There is also an architectural cost. Meta's rules run inside Meta's own infrastructure; AdOps reads and writes across the Marketing API with an access token, which adds a network hop, an API version to track and a token to keep valid.

## What constraints apply to both?

Both act through Meta's platform, so both inherit its restrictions. Meta's Business Help Centre states that automated rules cannot run on ads about social issues, elections or politics, and any tool driving the Marketing API is bound by the same rule. Both also read the same Insights numbers, which means both act on attributed, lagging data: a rule with a short reporting window will pause noise rather than a loser.

## Which one should an Indonesian advertiser pick?

Start with Meta Automated Rules. If every condition you need is a Meta metric and a 30-minute check is fast enough, there is no reason to add a vendor. Move to AdOps when the rule you actually want cannot be expressed in Ads Manager: comparing spend against a margin table in a spreadsheet, tagging campaigns with their own live ROAS, or scaling on a 15-minute cycle with a per-campaign log you can hand to a client. AdOps invoices in Rupiah through Duitku and starts with a 14-day trial once the signup email is confirmed.