Independent proof that your tracking is actually correct
A dashboard turning green proves a dashboard turned green. We verify tracking the way it should be verified: real transactions on real devices through every payment path, payloads read rather than presence-checked, consent tested from a clean profile, and everything reconciled against your own order records over a closed window. You get the evidence, so the result is checkable rather than a claim.
Free30 minutesNo obligation
QA & validation · what breaks
When independent verification is worth buying — QA & validation
- 01
A build you didn't do and can't verify
An agency or developer says it's working and nobody has tested it against reality.
- 02
Preview passes, and you're not sure production does
Which is the single most common false confidence in this field.
- 03
Numbers that changed and nobody knows why
A release shipped and the relationship to your orders moved.
- 04
A handover with no evidence attached
Documentation describing intent rather than demonstrating outcome.
QA & validation · the fix
What you get out of it — QA & validation
Evidence, not assertions
Captured payloads from real transactions, saved to your records.
A reconciliation you can repeat
Method and window stated, so your team can re-run it.
Every payment path tested
Not just the default one, which is where most gaps hide.
A clear pass or fail per event
Including anything we couldn't determine, listed as undetermined.
QA & validation · architecture
Why the numbers were wrong before you got here — QA & validation
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
QA & validation · diagnose
How we scope tracking qa and validation
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Agree what counts as correct
Before testing anything, so pass and fail mean something.
- 02
Walk the funnel live
Every payment method, real device.
- 03
Read the payloads
A tag that fires is not a tag that is correct.
- 04
Test consent from clean
Ordering and denial, per destination.
- 05
Test the duplicate paths
Refresh, back-navigation, direct visits.
- 06
Reconcile a closed window
The only check that isn't affected by the environment you tested in.
QA & validation · prove
How the work gets proven — QA & validation
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Your backend order or CRM records
- Every key event verified on a live transaction through every payment path.
- Payload evidence captured and annotated, handed over to you.
- Consent behaviour verified from a clean profile, per destination.
- Reconciliation over a closed window with method and matching key stated.
- Anything undetermined listed as undetermined rather than assumed passing.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
QA & validation · free audit
What we check in the free audit
- Agree what counts as correct
- Walk the funnel live
- Read the payloads
- Test consent from clean
- Test the duplicate paths
- Reconcile a closed window
Checked against
Your backend order or CRM records
Free30 minutesNo obligation
QA & validation · when not to buy
When you shouldn't buy this — QA & validation
We would rather say it now than three weeks into an engagement.
- You built it yourself and already reconcile monthly. That practice is the verification.
- You're about to replatform. Verify after, not before — most findings would be invalidated.
- Your spend is low enough that the verification fee is a large share of a month's budget.
- You want us to fix rather than verify. Skip this and go straight to the build; we'd rather do the work.
QA & validation · what we deliver
What's included in tracking qa and validation
Live transaction testing
Real device, real orders, through every payment method you offer.
Payload inspection
Types, formats, identifiers and hashing read from actual requests.
Consent verification
Clean-profile load, request ordering, and denial behaviour per destination.
Duplicate and guard testing
Refresh, back-navigation and direct URL visits.
Reconciliation
Backend orders against every platform for a closed window, matched on ID.
Evidence pack
Everything captured and annotated, yours to keep and re-check against.
Written guarantee
95%+ tracking accuracy
Measured against Your backend order or CRM records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
QA & validation questions, answered
An audit finds what's wrong across the whole setup. Verification tests whether a specific build does what it claims. Overlapping methods, different questions.
Yes, and that's most of what this is. We report what we find either way — including that it's correct, which happens.
You get the evidence and a prioritised list. Whether we fix it is a separate decision and there's no pressure attached.
Yes, and that's the point. The method, window and matching key are documented specifically so it doesn't depend on us.
WhatsApp