Every new campaign test gets a measurement window and stop-loss rules — so spend always has a verdict, never a shrug.
Campaign checkpoints are AdsBuddy's discipline mechanism: a new campaign test runs for a fixed window against pre-agreed success and stop-loss conditions. No judging a test too early, and no zombie campaigns spending forever without a verdict.
New campaign setups use a 7-day first checkpoint. AdsBuddy still watches delivery earlier: if a campaign is not spending after roughly 48 hours, or has no useful traction around day 4, it tells you what to change before the checkpoint closes. A 14-day window is only used when an existing saved setup explicitly says so or when AdsBuddy recommends extending a test because the data is still thin.
How it works
When a test starts, AdsBuddy captures a baseline — the checkpoint clock starts there, not whenever you next open the app.
During the window, the Dashboard and app page show simple progress and status while AdsBuddy watches the stop-loss conditions.
At the gate, AdsBuddy delivers a verdict: scale (lift confirmed), optimize (signal but not efficient yet), or pause (no demand at viable prices) — each with the next concrete step.
Once a country validates, scaling is reviewed from rolling performance. New countries go back through the same small-test discipline before they become scaling countries.
Stop-losses
Campaign setups carry explicit kill conditions — e.g. “CPA above target for 3 straight days” or “$250 spent with 0 paid conversions by day 10”. If one trips mid-window, you're alerted immediately with a one-click pause proposal instead of waiting out the window.
An app spending with noopen measurement window is flagged as a blocking issue on the Dashboard's “needs you today” strip — either pause the spend or rebuild the plan to start a fresh window. Unmeasured spend is the one thing AdsBuddy never lets slide quietly.