Tracking Loss Calculator
Your ad platforms report one number. Your books record another. Smart Bidding is spending your budget against whichever one is wrong, today.
Two numbers you already have. No form, no email, no call. You will know in under a minute whether the gap is worth investigating.
Find Out What Your Budget Is Actually Buying
Enter one month you can check. Every figure below comes from your own numbers. There are no industry averages here and no assumed loss rate, so you can verify the result against your records in a minute.
Take this from your store's own records: Shopify's Sales attributed to marketing report, an order export filtered by UTM source, or discount-code counts. Not from Google Ads and not from GA4, those are the systems being checked.
Same month. Total store orders include organic, direct and repeat purchases and will overstate the gap.27.7% understated
Your reported cost per order understates what an order actually costs you
These are the placeholder figures. Enter yours to replace this.
Enter your monthly ad spend. It is the one number that makes your position concrete.
spent on ads
Not one Conversion you can trace back to a campaign.
You are bidding in the same auctions as competitors whose platforms know which clicks became customers. Smart Bidding optimizes toward Conversions, and with none reported, yours has nothing to optimize toward. The platform spends your budget on the only signal it has left: clicks. You are paying for traffic while your competitors pay for customers.
- Which platform to cut, and which to double.
- Whether your last budget increase made money or cost money.
- What one customer actually costs you to acquire.
With Conversion Tracking in place, the other side of this tool returns your actual cost per order or lead, the cost your platforms claim, and the distance between the two. Today, none of those three numbers exists for your account.
This is a reconciliation, not a diagnosis. Attribution windows, view-through conversions, cross-device journeys, refunds and offline closes all produce legitimate gaps. Separating a legitimate gap from a defect is what the audit does.
A sale in Month 2 from a click in Month 1 appears in different months on each side. That is a legitimate gap, not a defect.
Trusted by brands worldwide
How This Number Is Calculated, In Full
A tracking loss calculator compares the Conversions your ad platforms report against the outcomes your books recorded, and values the difference. Every figure on this page comes from you. The calculator contains no industry averages, no assumed loss rate and no benchmark. It subtracts one number you supplied from another, so you can check the result against your own records in a minute. It makes exactly five assumptions, and all five are stated here rather than buried.
Spend is apportioned evenly across reported Conversions
When your platforms report more than your books, we divide your ad spend by the number of reported Conversions and multiply by the unmatched ones. Real spend is not distributed evenly across Conversions, so that figure is a scale, not an invoice.
Annual figures assume the month you entered is representative
The annual number is the monthly number multiplied by twelve. That is a projection, and it is the only one on this page. If the month you picked was unusual, the annual figure is unusual with it.
Unreported Conversions are never priced as lost revenue
When your platforms report fewer Conversions than your books, that revenue already reached you, so we never price the gap as recoverable money. We report the share of your real Conversions that are invisible to bidding, and what a Conversion actually costs you once they are counted. The only dollar figures on that side are your own spend divided by each Conversion count, and your own target.
Order value, deal value and close rate are treated as uniform
When you enter an average order value or deal value, every Conversion is valued at that figure, and your close rate is treated as uniform across leads. Real orders and real leads vary, so return and cost figures built on them are scales in the same way the apportionment is.
Total spend assumes your monthly figure was roughly constant
When you enter how long you have been running ads, total spend is your monthly spend multiplied by those months. It is arithmetic on two figures you supplied, not a loss estimate. If your spend varied a lot, the total varies with it.
Your reported cost per order or lead is your ad spend divided by the Conversions your platforms report; your actual cost is the same spend divided by what your books recorded. The distortion between those two figures is the same number as the discrepancy percentage, read as a cost instead of a count. One number, two readings, and you can verify either against the other.
When you have no Conversion Tracking, this tool shows no loss figure. Any number here would be a percentage we invented and applied to your spend. What we can state is your own spend, and the documented fact that Smart Bidding has no Conversion data to learn from.
A discrepancy is not proof of a tracking defect. Attribution windows, view-through Conversions, cross-device journeys, refunds and offline closes all produce legitimate gaps between a platform and a ledger. A mismatched attribution window is the most common harmless explanation. Separating a legitimate gap from a real defect is the work, and it is what the audit does.
What Actually Produces a Gap
A gap between reported Conversions and recorded outcomes has a direction, and the direction narrows the cause. Read the group that matches your result. Each mechanism below is documented by the platform itself, not inferred by us.
Your platforms reported fewer than your books
Four documented mechanisms stop a Conversion that really happened from ever reaching the platform. All four are recoverable, and which one applies is what an audit establishes.
Consent-driven signal loss
When a visitor denies consent, the Conversion still happens but the identifiers that attach it to a click do not.
Browser and iOS restrictions
A Conversion that completes outside a short window after the click can no longer be matched to it in the browser.
Cross-domain breakage
When your landing page and your checkout sit on different domains, the click identifier has to be carried across deliberately or it is lost at the boundary.
Offline Conversions never returned
A lead that closes weeks later on a call or an invoice is revenue your books record and your platform never hears about.
Your platforms reported more than your books
The usual cause is the same event being counted twice, once by the browser and once by the server, without the two being matched to each other.
Duplicate firing across browser and server
Running a browser pixel and a server-side API together doubles every Conversion unless each pair carries a matching identifier.
Find Out Which Mechanism Is Producing Your Gap
The number above tells you a gap exists. It cannot tell you which of the five mechanisms is causing it, because that is only visible in your actual tag configuration, your consent setup and your platform settings.
A free audit reads your live setup and names the mechanism. Written findings, one business day, no call required.
Free. Written findings within one business day. Most people book the call afterward.
Questions About Tracking Loss
What is a tracking loss calculator?
A tracking loss calculator is a reconciliation tool that compares the Conversions your ad platforms report against the outcomes your own books recorded, then values the difference. It uses no industry averages and no assumed loss rate, so every figure it returns traces back to two numbers you supplied.
Does a gap between my platform and my books mean my Tracking is broken?
No. A discrepancy is a reason to investigate, not a diagnosis. Attribution windows, view-through Conversions, cross-device journeys, refunds and offline closes all produce legitimate gaps. A mismatched attribution window is the most common harmless explanation, and separating that from a real defect is what a free audit establishes.
Why does this tool show no revenue figure when my platforms under-report?
Because that revenue already reached your books. Nothing was lost except the signal. Pricing unreported Conversions as recoverable money would be a claim this tool exists to refuse, so the under-reporting result is expressed as the share of your real Conversions that are invisible to Smart Bidding and as your actual cost per Conversion, never as recoverable revenue.
Why do my Google Ads Conversions not match my Shopify orders?
Google Ads counts a Conversion against the click that earned it, within an attribution window, and only when the identifier survives the journey. Shopify counts an order when it is paid. Consent refusals, browser cookie limits and cross-domain checkouts each break that link while the order itself completes normally.
Why do GA4 and Google Ads report different Conversion numbers?
The two products count differently by design. GA4 attributes on its own model and reporting identity, Google Ads attributes to the click. A difference between them is expected and is not itself a defect. A difference between either platform and your ledger is the one worth investigating.
How much of a discrepancy is normal?
There is no published normal, and we will not invent one. What matters is whether the gap has an explanation you can name. A gap fully accounted for by attribution windows and refunds is fine at any size. A gap nobody can explain is worth auditing at any size.
Can a tracking discrepancy actually be fixed?
Most of it, yes. Consent-driven loss, cross-domain breakage, duplicate firing and unreturned offline Conversions each have a documented remedy. Some loss is structural and permanent, and we will say which part of your gap falls into that category rather than promising to recover all of it.
Do I need Server-Side Tracking to close the gap?
Not always. Server-Side Tracking recovers signal the browser drops, which addresses the cookie and consent mechanisms directly. It does not fix a Conversion that was never configured or one firing on the wrong action. The audit establishes which problem you have before anything is rebuilt.
Is my situation too unusual for a standard service?
Subscriptions, multi-domain journeys, dynamic revenue values, multi-region consent and long offline sales cycles are the situations that produce the largest gaps. Those are scoped from your actual stack rather than quoted from a list, which is what a scoping conversation is for.
A Number You Can Check Beats a Number You Are Told
Every figure on this page came from you, which is the only reason it is worth anything. The next step is the same idea applied to your actual setup: a written audit that reads your live configuration and names which mechanism is producing your gap, before anything is rebuilt.
