Facebook automation rules

Configure rules in Autolaunch → FB automation rules. They use Meta metrics and run through the extension in an open browser profile. They are separate from the tracker's automation rules for traffic streams.

Create and enable a rule

1. Connect the extension with your own key and sync the account.
2. Create a rule template. Choose campaign, ad set or ad as the object level.
3. Set conditions, currency and action. Choose a cooldown between actions and a maximum number of actions per day.
4. For budget changes, set permitted limits. Campaign and ad set budgets can be changed; individual ads do not have their own budget.
5. Bind the template to a specific object ID and profile. New bindings are disabled: review and enable them separately.

Buyers manage their own rules and objects; team leads manage their permitted team. Only one active executor can be assigned to an object, preventing competing commands from different profiles.

Conditions and actions

Metrics include spend, impressions, clicks, CTR, CPC, leads and CPA from Meta. They cover the ad account's current day, currency and time zone. Select the relevant event type for leads. Unknown metrics are not treated as zero: if Meta has not returned statistics, the rule does not execute an action.

Actions can pause or enable an object, or change a campaign or ad set budget within configured limits. Enabling ads and increasing budgets can incur spend; set limits before enabling a binding.

Minute cycle and connectivity

The extension checks rules approximately once a minute. Keep the browser profile open with a valid Meta session and tracker connection. Browser scheduling and network delays can postpone a cycle; execution at an exact second is not guaranteed.

The panel shows executor status and its last connection. Closing the profile stops execution. Expired commands are not replayed when it reopens. Authorization time is checked against the tracker, so changing the computer clock does not extend a permission.

Action history and uncertain outcomes

The history records the object, rule version, metrics, before and after values, and result. Each command receives a single-use authorization. If Meta's response is lost after a write, the result becomes Needs review. The command is not blindly retried; the extension reads the object's current state first.

Pausing a binding stops future checks for it. Before changing important conditions, review actions already sent in the history. Campaign statuses are synchronized independently of enabled rules.