Why Paceloop flagged your sales target as unrealistic
Last updated: 1 August 2026
Paceloop projected your last 90 days forward and measured the gap to your target. When closing that gap needs a lift no single lever plausibly delivers in one cycle, the verdict is "Not realistic in one cycle" — and Paceloop recommends a lower number instead of telling you to spend more.
The full refusal reads:
"Honest read: no single lever moves [the required lift]% in one cycle. Committing to this anyway wastes ad spend and morale. Set [the recommended target] — a target you can actually pace against — and re-raise next cycle."

The five verdicts
Every pressure-test lands on one of five verdicts, graded by the effort your target requires over your current trend:
- "Below your current trajectory" — the target is under what you're already doing
- "Realistic" — within about 10% over trend
- "A stretch — doable with focus" — up to about 30% over trend
- "Aggressive — high risk of slipping" — up to about 60% over trend
- "Not realistic in one cycle" — beyond that
Where the recommended number comes from
The recommendation is your own 90-day trend projected through the cycle, plus a modest 15% step (for metrics where down is good, minus 15%). It is a number your history says you can pace against — not a number pulled from ambition.
Paceloop never counters with "increase your budget". If a target is out of reach, the only honest fix it will offer is a lower target.
The lever table
Under the verdict, the table "If one lever had to close the gap" shows what each lever alone would need to do, marked "Plausible" or "Unlikely" against what each typically moves in a single cycle — conversion up to ~30%, average order value ~25%, traffic ~40%, repeat rate ~50%.

What to do next
- Adopt the recommended number — the "Use recommended" button sets it for you. You can re-raise next cycle from a higher baseline.
- Or edit the target to something between trend and your original ask, and pressure-test again.
- Or keep your number anyway: "Keep this target — find my constraint" always works. Paceloop states its case; it never blocks you.

When there's no trend at all
On a store with no usable history, Paceloop refuses to recommend any number: "with no history to read there's no trend to build on, so there's no target worth recommending — any number … would be invented." See what "Not readable" means for how Paceloop handles missing data everywhere else.
A tool that only ever says yes to your targets isn't checking them. The flag means the check is real.
Related: why a split gets refused · set up Paceloop from scratch