CASE STUDY / VERIFIED

Flat for the best part of a week. The platform said everything was fine.

A Scottish musician's campaign had stalled. We repaired the attribution signal and ran agents over the creative and the budget. Under two sales a day became over nine across the paid run, on lower spend, a 6.3x return verified on Meta's own API and reconciled to the bank. Meta delivery ran nine days, 12 to 20 May 2026.

WHAT YOU CAN CHECK

The claims on this page, and how they were checked

6.3x return.

Checked against Meta's own API and reconciled to money that landed in the bank, not read off the platform's scorecard. Treat it as a floor: attribution was only repaired in the last day or two of the run, so it is what we could prove rather than everything that happened.

Under 2 a day to over 9 a day.

The sustained rate across the paid run, on lower spend. The closing four days ran hotter again, peaking past fourteen, which is a peak and not the run rate.

Nine days of delivery.

Meta delivery ran nine days, 12 to 20 May 2026. The longer twelve-day figure you may see elsewhere is the reconciled window running to the campaign close, which is a different thing.

The client.

She is a Scottish musician and is never named here, consent held for the story as told here. What is live, what is roadmap and what we have not built is set out in the facts table.

See the full facts table →

The stall.

A Scottish musician came to us with a campaign that had flatlined. Flat for the best part of a week, money going out, nothing coming back. And the platform's own reporting told her everything was fine. That gap between what Meta claimed and what the bank account said is the whole disease we treat.

The look.

We plugged her accounts into the warehouse and did what a dashboard can't: reconciled the platform's numbers against real sales. The attribution was broken at the timing level. Conversions were landing but reporting late and mis-stamped, so the algorithm was flying blind, and the reporting layer was papering over it.

The fix.

We repaired the server-side signal so the platform could finally see what was actually converting. Then we ran agents recursively over the creative and the budget: review, reallocate, redeploy, day after day, at a pace no weekly meeting can match.

The scoreboard.

Two a day became over nine a day across the paid run, on lower spend, and the closing four days peaked past fourteen. A 6.3x return, and here's the bit that matters: that figure is verified against Meta's own API and checked against money in the bank, not taken from the platform's scorecard. Most agencies report what the platform tells them. We report what actually happened, and when the two disagree we can show you exactly where and why.

THE KICKER

The fix wasn't a clever ad. It was seeing the data properly. Once the machine could see truth, the decisions were obvious.

WHAT THIS MEANS FOR YOU

The villain in this story is in your accounts too. Somewhere, a platform's scorecard and your bank disagree, and the disagreement is costing you money you can't see. The machine that found and fixed it here is the same machine we plug every client into. We ran it on our own business first; we run it on our proving ground every day. Nothing gets shipped to a client that we haven't run on ourselves.

Their own ChatGPT. Their own numbers. Answers they can check.

The fix wasn't a clever ad. It was seeing the data properly.
Book the full demo

Your version of this story starts with one look at the data.