Are you actually ready for server-side tracking?
Nine questions, and two of them can end the conversation on their own. If you haven't measured a gap between your own records and what the platforms report, server-side is cost without benefit. If nobody will own the container after handover, an unowned one is worse than none — and we'd rather tell you that here, free, than sell you a build that quietly stops working in six months.
Free30 minutesNo obligation
Are you ready for server-side tracking?
Nine questions, and two of them can end the conversation on their own. If you haven't measured a gap, server-side is cost without benefit. If nobody will own the container after handover, an unowned one is worse than none — we'd rather tell you that here than sell you a build that quietly stops working.
Have you measured a gap between your own records and what the platforms report?
This is the precondition. Without a measured gap, server-side is cost without benefit.
weight 5Is the gap worse in Safari than in Chrome?
If both show the same gap, ITP isn't the cause and server-side won't fix it.
weight 4Is your consideration window longer than seven days?
Safari caps JavaScript-set cookies at seven days.
weight 3Can your checkout lose the conversion event?
Wallet payments and hosted payment pages can be abandoned after payment completes.
weight 3Can you reach your order or CRM records via a webhook or API?
Without this, a server container is only a proxy for browser events.
weight 4Will a named person own the container after handover?
Infrastructure with no owner degrades quietly.
weight 5Have you decided where it will be hosted, in an account you control?
weight 3Are your current browser-side events correct, as opposed to just present?
Moving a wrong event to a server produces a wrong server event, delivered more reliably.
weight 4Do you have DNS access to create a tagging subdomain on your own certificate?
weight 2
Readiness check · what breaks
What this tool is for — Readiness check
- 01
You're being pitched server-side
By us or anyone else, and want to check the premise.
- 02
You've measured a gap
And want to know whether this is the right fix.
- 03
You're scoping a migration
And want the preconditions clear before you start.
Readiness check · the fix
What you get out of it — Readiness check
A readiness verdict
Including 'don't buy this yet', which is a real outcome.
The preconditions you're missing
Ordered by weight.
Weights you can argue with
Shown next to each question.
Readiness check · architecture
Why we publish a tool that talks people out of buying — Readiness check
Server-side is the main thing we sell, and it's the wrong answer for a meaningful share of the people who ask about it.
- 1
No measured gap means no benefit
If your reported conversions already match your records, a migration changes nothing you'd notice and costs real money.
- 2
Same gap in Safari and Chrome means ITP isn't the cause
That finding costs a day of segmentation and can save the entire build.
- 3
An unowned container degrades quietly
Certificates expire, destinations change templates, and nobody notices until a quarterly review.
- 4
Correctness has to precede durability
Moving a wrong event to a server produces a wrong server event, delivered more reliably.
Readiness check · diagnose
What this tool cannot tell you — Readiness check
Stated up front, because a tool that implies more confidence than it has is worse than no tool. These are checks you have to run yourself.
- 01
Whether you have a gap
It asks whether you've measured one. Measuring it is a reconciliation you run yourself.
- 02
How large the benefit would be
That depends on the size and composition of your gap, and only part of any gap is addressable.
- 03
Whether your team will actually own it
It asks. Answer honestly — this is the question people most want to answer optimistically.
- 04
Anything about your account
No access. Everything it knows, you told it.
Readiness check · prove
How to confirm the result — Readiness check
Against your own records, not against the tool's output.
Source of truth
a reconciliation of your own records against each platform, segmented by browser
- A gap measured and segmented by browser before any decision.
- A named owner identified and agreed.
- Backend webhook or API access confirmed.
- Hosting decided, in an account you control.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked after your next site release, which is when most breaks happen.
Readiness check · free audit
What we check in the free audit
- Whether you have a gap
- How large the benefit would be
- Whether your team will actually own it
- Anything about your account
Checked against
a reconciliation of your own records against each platform, segmented by browser
Free30 minutesNo obligation
Readiness check · when not to buy
Why this isn't gated — Readiness check
There's no email form in front of it, and that's deliberate.
- A tool you have to pay for with your contact details is a lead form wearing a costume. If this is useful, it should be useful without a transaction.
- Everything it does runs in your browser. There is no endpoint, so there is nothing for us to collect even if we wanted to — open your network tab and check.
- It will tell you when you don't have a problem. That outcome costs us a sale and happens regularly, which is the point of publishing it rather than putting it behind a call.
- If it does find something and you'd rather fix it yourself, the reference pages on this site cover the how. Hiring us is one option, not the conclusion.
Readiness check · what we deliver
What it checks
A measured gap
The precondition. Without it there's nothing to fix.
Browser segmentation
Whether the gap is worse in Safari, which decides whether ITP is even your problem.
A named owner
Weighted as heavily as the gap, because an unowned container degrades.
Backend access, hosting and DNS
The practical blockers, better found now than mid-build.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
If the tool found something and you'd rather not fix it yourself: we repair the root cause in your existing setup and verify it on a live conversion.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than the instance. Money events from your own records through a first-party container on your subdomain.
- First-party server container on your own subdomain
- Events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Readiness check questions, answered
Then don't buy server-side yet, from us or anyone. Work the list — several items are free and worth doing regardless.
Because a container nobody maintains stops working, and then you've paid for something that quietly degraded. It's the failure we most want to avoid selling you.
Yes. Without a measured gap, server-side is buying a solution to a problem you haven't confirmed you have.
We measure your gap live on your own account. If it's small we say so — that outcome costs us the sale and happens regularly.
Free · 30 min
Get your gap measured free before deciding
WhatsAppFree30 minutesNo obligation
