Why Paceloop refused your split
Last updated: 1 August 2026
Your sub-targets, multiplied through your store's real funnel, imply a different objective than the one you set — off by more than ±5%. So Paceloop refused the split and did not save it. The banner heading says exactly that: "This split doesn't add up — not saved".
The refusal always quotes both numbers:
"This split implies [one number], but your objective is [your number] at your current funnel math […]. The plan doesn't add up: raise a sub-target or lower the objective."

How the check works
A split gives 2–3 funnel factors their own targets — as the split step puts it: "Give 2–3 of its funnel factors their own targets and Paceloop checks the plan adds up — the factors must multiply back to the objective, on your store's real numbers."
The funnel identity is fixed: revenue = sessions × conversion rate × average order value. Any factor you didn't give a target keeps its current level, read live from your store — never from an assumption. The check then multiplies everything through and compares the implied objective to your stated one. More than ±5% apart, and the split is refused.

When the check can't run at all
If a factor without a sub-target can't be read from your store, Paceloop doesn't substitute a guess — it declines to check: "We can't check this split right now: [the metric] can't be read from your store. Enter a target for it, or come back when the data is available." A check that runs on invented numbers wouldn't be a check. See what "Not readable" means.
What to do next
- Raise the sub-target the refusal points at — the funnel line under the banner shows each factor's current level, so you can see which one falls short.
- Or lower the objective to what the sub-targets actually imply.
- Then "Check & save split" again. When it passes you'll see "Split saved — it adds up".
- Or skip the split entirely — "Skip — one objective is fine" is always available. A split is optional; an objective that adds up is not.

A split that doesn't multiply back to the goal is a plan that quietly promises two different outcomes. Paceloop refuses it now so week 3 doesn't.
Related: why a traffic sub-target gets refused · why a target gets flagged as unrealistic · set up Paceloop from scratch