The 11 actions an AdOps rule can execute

AdOps can execute 11 actions on the campaigns a rule matches, grouped in the action picker as General, Budget, and Name or text. Every action is written to Meta through one instrumented wrapper, and budget and name actions record the value before and the value after on the result row for that campaign.

What are the 11 actions?#

Group	Action	Key	What it does
General	Notify	notify	Marks the condition as met on this campaign
General	Start	start_campaign	Writes status ACTIVE
General	Pause	pause_campaign	Writes status PAUSED
General	Delete	delete_campaign	Writes status DELETED
General	Duplicate	duplicate_campaign	Submits a deep copy of the campaign
Budget	Increase budget	increase_budget_campaign	Raises the daily budget, capped at a maximum
Budget	Decrease budget	decrease_budget_campaign	Lowers the daily budget, floored at a minimum
Budget	Set budget	set_budget_campaign	Writes an absolute daily budget
Name and text	Add to name	add_name_campaign	Appends a rendered template to the name
Name and text	Remove from name	remove_name_campaign	Strips a substring from the name
Name and text	Replace text in name	replace_name_campaign	Swaps one substring for another

Duplicate is worth a line of its own. It posts an async batch to Meta asking for a deep copy of the campaign under a generated job name, so Meta clones the whole structure rather than AdOps rebuilding it field by field.

How do budget changes work?#

A budget action carries an amount, a cap, and a value type. The value type is value for a fixed amount, percent for a percentage of the current daily budget, or custom_metric to pull the number from a Google Sheets custom metric.

Two details make this safe enough to leave running. First, AdOps re-reads daily_budget from Meta immediately before a budget action executes, so a change made in Ads Manager five minutes earlier cannot cause a write based on a stale figure. Second, the projected budget is floored to an integer and clamped: when an increase would exceed the maximum cap, AdOps writes exactly the cap, and when a decrease would fall under the minimum, it writes exactly the minimum.

Set budget skips the arithmetic and writes the absolute figure you supplied.

What can go into a campaign name?#

Name actions also re-read the live campaign name from Meta before writing. Add to name then builds its new text from a multi-line template where each brace-wrapped line is expanded at execution time.

Token	Expands to
{date}	The execution date
{time}	The execution time
{metric|<metric_key>|<date_preset>}	A live Insights value for that metric and period
{metric|<campaign_field>}	A field read straight off the campaign object
{metric|custom_metric|<id>}	A computed custom metric
{custom_metric|<id>}	A computed custom metric

Parts are joined with a separator you supply, and the result is placed by one of three modes. TEXT appends the rendered string as-is. APPEND adds it after the bot separator, a marker AdOps writes so its own section of the name stays distinct from the part a human wrote. OVERWRITE replaces everything after that marker, which is what keeps a nightly performance tag from stacking up forever.

Remove from name and Replace text in name are the cleanup pair: one strips a substring, the other swaps it, and both record the old and new name.

How do action cooldowns stop a rule thrashing?#

Each task can carry an action frequency, which is a cooldown on that action for that campaign, entirely separate from how often the rule is evaluated. A rule can be checked every 15 minutes and still raise a given campaign’s budget only once every 2 hours.

Eleven options are available: 15 minutes, 30 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12 hours, once a day, once in 2 days, once in 3 days, and once in a lifetime. Day-based cooldowns snap to midnight, and once in a lifetime sets the next permitted execution to the year 2100, which is how a tag-once or duplicate-once rule is expressed.

Five of the 11 actions accept a frequency: Notify, Duplicate, Increase budget, Decrease budget and Set budget.

When a cooldown blocks an action, AdOps does not stay silent. It writes an explicit skipped result carrying the reason next_execute_not_reached, the time the cooldown expires, and a step recording that the evaluation was skipped. The log answers why nothing happened instead of leaving a gap.

What is recorded when an action runs?#

Every one of the 11 writes to Meta goes through a single wrapper that logs the request URL, the request body and Meta’s response. A failure pushes the function name, the message, the stack, the exact request body and Meta’s error response into a deduplicated error log, so a recurring API fault appears once with an occurrence count rather than as thousands of identical lines.

Budget and name actions additionally stamp a before value and an after value onto the campaign’s result row, which is what the Value Changes block in the log detail renders as Before and After.