Case story
Your dashboard said you spent 9x what Google says you spent.
An EU kids-interior brand running five locale stores (anonymized).
The problem nobody sees
Ad-spend numbers flow from platforms into dashboards through daily syncs. When a sync re-pulls a day that already exists and the pipeline does not deduplicate perfectly, the same campaign-day lands twice. Then three times. Nobody notices, because the number only ever moves in a believable direction: up.
What Vibel found
A reconciliation pass compared the platform's own reported spend against the stored figures for a 30-day window. Google Ads spend read ~9x what Google itself reported for the same period, with up to 17 copies of the same campaign-day stacked in the store. Every downstream number built on it, MER, blended ROAS, budget advice, was quietly wrong.
The fix, and the guarantee
- Duplicates were identified deterministically and removed. The window re-measured within ~1% of Google's own figure, the residual explained by a status filter.
- The root cause, daily snapshots written without an idempotency key, was fixed so a re-pull replaces the day instead of stacking it. A day's spend can legitimately change while the day runs; the fix keeps the latest platform figure, never a stack.
- Meta was audited with the same method and found clean, which is the point: the method is checkable, not vibes.
Why this matters
Most tools ask you to trust their pipeline. Vibel reconciles its stored numbers against the platform's own reporting and tells you when they disagree, because a profit platform that cannot audit its own inputs is just confident, not correct.
Every number, checked against the source.
Vibel reconciles spend and traffic against the platforms themselves, and tells you when they disagree.