The logic behind cutting budget when CPA runs 20% over

The draining part of paid ads is not building campaigns. It is opening the dashboard every morning, seeing what yesterday spent and how many conversions came in, then deciding whether to raise or cut.

The rule behind that decision is actually fixed: CPA above target means cut budget; below target with volume means raise it. The human part is only execution.

But automation here spends real money

So we did not ship full automation on day one.

Today's default: after three consecutive days of CPA running 20% over target, the system alerts you with a recommended action, and it executes only once you confirm. Not because it cannot be automatic — because before enough attribution data accumulates, the cost of a wrongly cut budget outruns the labour it saves.

Attribution flows back through GA4 and each platform's pixel, with delay. The CPA you see today may be pulled down tomorrow by conversions that land late. The three-day window exists to damp that noise.

The hard cap lives server-side

Automatic or manual, the monthly spend ceiling is enforced on the server. That is not a seatbelt for the algorithm — it is one for people. Adding an extra zero to a daily budget by accident is far more common than a runaway algorithm.

When full automation turns on

When two conditions hold together: attribution data is deep enough to model a stable conversion-delay curve, and you are willing to turn it on.

The second condition matters more.