Automation
Nobody was watching.
Nothing waited.
Rules that carry their own time and week-days, running in the account’s timezone — so a campaign that turns at 02:00 isn’t still burning when you get in.
Write it once.It keeps the hours.
conditions · actions · a time
Conditions
Actions
A clause is field, window, operator, value — every part a menu. Clauses inside a group are ANDed; a second group would be ORed against this one.
Then it gets a time and a set of week-days, not an interval. The delay override holds it back so attribution can land before the rule judges anything.
At 02:15 it ran, in the account’s timezone, and wrote down what it saw. That log line is the whole promise: the decision was made once, by you, in daylight.
How it runs
A schedule, not a polling loop
On your clock
A time and a set of days
Every rule holds an hour and the week-days it runs on, evaluated in the account’s own timezone — so 02:15 means 02:15 where the account lives, not where the server does.
Let the numbers land
A delay you set per rule
Attribution arrives late. The delay override holds a rule back by a set number of hours so it judges a settled figure rather than the one that was on screen at midnight.
It says what it did
One line per decision
A run writes what it saw and what it changed, against the rule that made the call — including the runs that decided to do nothing.
Before you enable one
What the product tells you, in its own words
Two messages worth reading before the first rule goes live. Both are taken from the dashboard rather than written for this page.
Automation will work properly ONLY on campaigns created in Big Pipes AND not being changed outside Big Pipes.
A rule reasons about state it put there itself. Edit a campaign in the network’s own UI and the two views drift apart — the rule keeps acting on the one it knows.
This automation is not fully configured. Please configure it before enabling it.
A rule missing a condition, an action, or a time can’t be switched on. It stays a draft rather than being enabled into a state where it would never fire.
Get started
Bring one keyword list.
Leave with a batch.
Book a 20-minute working demo — we’ll build rows from your template, fire them, and watch the creation events come back on the call.
No credit card. No migration project.