Services · Measurement

Numbers you can make a budget decision on

Every ad platform reports its own contribution generously. Add up what Meta, TikTok and Google each claim and the total is often 30% to 80% more than the revenue your store actually took. That gap is not a rounding error. It is the reason two sensible people can look at the same month and disagree about whether it was good — and at a small budget, one wrong call can cost a quarter's growth.

Measurement

When the platforms disagree with the bank

Meta claims 3.1x. TikTok claims 2.2x. Google, if you run it, claims many of the same orders again. The founder divides total revenue by total ad spend, gets 1.7x, and has to decide whether to spend more next month without knowing which of those numbers to believe. The instinct is to pick whichever figure supports the decision already made. For a small DTC brand the trouble usually starts lower down: a pixel firing twice on the thank-you page, purchases tracked only in the browser so a fifth or more never reach the platform, or a theme update that quietly broke the checkout event weeks ago. Before anyone argues about attribution, the events themselves have to be right.

What the work is

Measurement, in four parts.

01

Events checked before anything else

Every engagement starts with the ads audit, and the pixel is part of it: do purchase events fire once, with the right value and currency, and are the add-to-cart and checkout events there at all? We place a real test order and follow it end to end. On Starter and Growth you get the fixes as a step-by-step list your developer or store app can follow; most take an hour or less.

02

Server-side events on Scale

On Scale we set up the Conversions API on Meta and the equivalent on TikTok, with event IDs matched against the browser pixel so nothing is counted twice. Usually that means configuring your store's native integration properly rather than building anything custom. We then track event match quality as a standing number in the monthly report, not a box ticked once at setup, because a poorly matched account is optimizing on bad information every hour of every day.

03

A blended number everyone agrees on

Before the first month starts we agree the one number the engagement is judged on — usually total store revenue, or new-customer revenue, over total ad spend — and write down exactly how each part is calculated. Platform ROAS stays in the report as a directional signal for day-to-day decisions, clearly labeled as such. Disagreements after that are about strategy, which is a far more useful argument to have.

04

A monthly report you can read without us

One report a month, with the blended number at the top, platform detail beneath it, definitions written on the page, and a short note on what changed and why. If you already run a post-purchase 'how did you hear about us' survey, we read it alongside. When a number moves, the report is where you find out why before you have to ask.

What you receive
  • Pixel and purchase-event review in the ads audit, with a written fix list
  • Conversions API and tracking setup on Scale, with deduplication checked
  • An agreed blended number, defined in writing before month one
  • A monthly report with blended and platform views side by side
Timeline

The pixel check happens in audit week. On Scale, Conversions API setup usually takes one to two weeks, depending on your store platform and apps. The blended baseline needs about 30 days of clean data before it is worth trusting, so the first month's report sets the line and the second month gives the first real comparison.

Who this is for

Any brand where the ad platforms and the store disagree by more than a little, where purchase tracking was installed by an app nobody has checked since, or where a decision about spend has stalled because nobody trusts the numbers. Full Conversions API setup comes with Scale; on Starter and Growth we check your events and write the fixes for you to apply.

What it costs

Priced on the pricing page — no quote needed to find out.

Questions

About this service.

Do we need server-side tracking at our size?
Usually, yes, once you spend more than a couple of thousand dollars a month on Meta. Browser-only tracking tends to miss a meaningful share of purchases, and the platform then optimizes on an incomplete picture. On most store platforms the fix is configuring the native integration correctly, not custom development. Setup is included on Scale; on the other plans we write the steps for you.
Can you prove the ads are incremental?
Not with the certainty a large brand can buy. Proper holdout tests switch ads off in matched regions for weeks, and they need far more than $15,000 a month in spend to give a readable answer. At this size, clean events, an agreed blended number and a careful before-and-after read whenever a platform is paused or a budget changes sharply are the honest guide, and we tell you how confident each read is.
Can you work with our developer?
Preferably. We specify and check; your developer implements wherever code is involved. That is faster, and it leaves the knowledge with your team rather than with us.

All questions →

Send us your ad account

Start with the one-week ads audit. We will tell you what we would change in the first month, and the $160 is credited against it if you continue.

Get in touch