Module

Auto Rules

Automated Facebook ad management: a “condition → action” rule is checked on a schedule and runs actions when all conditions are met.

Access

AdminFullManagerFullTeam Lead BuyerTeamOwnBuyerOwn

Rule scope depends on role: Buyer — Personal only, Team Lead — Personal and Team, Manager — all three (including Company).

Screen blocks

Rules list — Name, Details, Status (Active/Disabled), Scope (Personal/Team/Company).
Condition builder — 1–10 conditions (AND). Type Key — an ad field (Facebook account / ad-account / campaign / adset / ad name or ID, or Sub Id 1–20) — or Metric — a numeric value with an operator and threshold.
Actions picker — 1–5 actions: Pause/Resume campaign, adset or ad; Increase/Decrease budget by percent; Increase/Decrease budget by amount.
Schedule — frequency (every 15/30/45 min or 1 hour), timezone, check start and end time.
Execution history — a paginated list of past rule runs — status (Success / Failed) and time; filter by date range, rule, action type, team and user. Open a run to inspect it.

Functions

Function	Description	Admin	Manager	Team Lead Buyer	Buyer
Rule builder	Conditions (AND) → actions; scope Personal/Team/Company by role.	Full	Full	Team	Own
Check schedule	Frequency, timezone, time window; Active/Disabled status.	Full	Full	Team	Own
Fire notifications	When a rule fires — a Telegram notification to owners of affected accounts.	Full	Full	Team	Own

Statuses

Active — enabled — the rule runs on its schedule and can trigger actions.
Disabled — turned off — the rule does not run and is never evaluated.

Scenario — «Stop-loss rule»

Conditions: Spend > $100 AND ROI < 50% (AND logic).
Action: “Pause campaign”.
Scope: Personal (own accounts only); frequency — hourly.
Status Active — and get a Telegram notification when it fires.

Good to know

Rules are stateless: each cycle is a fresh check of current values. A reverse action (Resume) runs only if it's configured.
All conditions use AND logic — every one must hold.
Execution history: browse past runs and open any one to see its triggered conditions, executed actions and — if it failed — the error message. A Telegram notification is also sent when a rule fires.
Metric conditions work with both Facebook (Spend, CPC, CTR…) and the tracker (Registers, FTD, CPI…).
Key operators: Equal / Not equal / Contains / Not contains / In / Not in. Metric operators: > < ≥ ≤ = ≠.
Metric conditions cover Facebook metrics (Spend, Impressions, Reach, CPC, CTR, CPM, Link clicks, Leads, Registrations, Purchases and their costs) and tracker metrics (Unique clicks, Registers, FTDs, RDs, CPI, CPR, Cost per Deposit).
The scheduler checks every minute which rules are due; an action that would leave an entity in the state it's already in is skipped (reason: already in target state).

Screen blocks

Rules list — Name, Details, Status (Active/Disabled), Scope (Personal/Team/Company).

Condition builder — 1–10 conditions (AND). Type Key — an ad field (Facebook account / ad-account / campaign / adset / ad name or ID, or Sub Id 1–20) — or Metric — a numeric value with an operator and threshold.

Actions picker — 1–5 actions: Pause/Resume campaign, adset or ad; Increase/Decrease budget by percent; Increase/Decrease budget by amount.

Schedule — frequency (every 15/30/45 min or 1 hour), timezone, check start and end time.

Execution history — a paginated list of past rule runs — status (Success / Failed) and time; filter by date range, rule, action type, team and user. Open a run to inspect it.

Functions

Function	Description	Admin	Manager	Team Lead Buyer	Buyer
Rule builder	Conditions (AND) → actions; scope Personal/Team/Company by role.	Full	Full	Team	Own
Check schedule	Frequency, timezone, time window; Active/Disabled status.	Full	Full	Team	Own
Fire notifications	When a rule fires — a Telegram notification to owners of affected accounts.	Full	Full	Team	Own

Good to know

Rules are stateless: each cycle is a fresh check of current values. A reverse action (Resume) runs only if it's configured.

All conditions use AND logic — every one must hold.

Execution history: browse past runs and open any one to see its triggered conditions, executed actions and — if it failed — the error message. A Telegram notification is also sent when a rule fires.

Metric conditions work with both Facebook (Spend, CPC, CTR…) and the tracker (Registers, FTD, CPI…).

Key operators: Equal / Not equal / Contains / Not contains / In / Not in. Metric operators: > < ≥ ≤ = ≠.

Metric conditions cover Facebook metrics (Spend, Impressions, Reach, CPC, CTR, CPM, Link clicks, Leads, Registrations, Purchases and their costs) and tracker metrics (Unique clicks, Registers, FTDs, RDs, CPI, CPR, Cost per Deposit).

The scheduler checks every minute which rules are due; an action that would leave an entity in the state it's already in is skipped (reason: already in target state).