The Operator and approvals
What moved and why, three ways out priced in cash — each action waits for you.
Analytics → Operator (Pro). It reads two periods of your store, finds the line that took the money — an ad set, a product’s returns, a channel — and prices three ways out of it. An action such as pausing an ad set or moving budget is shown with exactly what it will change.
- Read the case and the three options.
- Approve one, or reject them all.
- An approved action on Meta or Google is applied for you and recorded in the actions log; anything else is left for you to do.
It also watches streaks: an ad set under 0.8× on profit three days running is prepared for a pause, and one over 2× two days running for one +20% budget step. The rule only notices; the action waits for you like every other. With an API key, the same case can be read from your own tools at /api/operator/read — read only.
Your rules, under the case: tick which kinds of prepared action you are happy to approve together — pauses after three days under 0.8×, pauses of ad sets selling at a loss, one budget step after two days over 2×. One button then approves what they selected, after showing you the list; at most five at a time. A tool with an API key can propose an action too: it appears marked as suggested from outside, unpriced, with Approve and Dismiss, and is never selected by a rule. At the top, your record: what the operator has prepared now, and what you approved, carried out and undid in the last 30 days.
Nothing changes without your approval. An approval names the exact action shown; if the figures have moved since, it is refused rather than applied to something different.
Not answered? Write to hello@profflow.co — usually answered within a day.