Browser-only conversion tracking quietly loses a large slice of events to ad blockers, iOS App Tracking Transparency, and privacy-strict browsers. This is a design for a drop-in measurement layer modeled on the Meta Pixel + Conversions API pattern: a lightweight browser snippet fires a standard event taxonomy (Landing, Lead, Booking, Purchase, Call), and a server-side Conversions API hardens those events against ad blockers and cookie loss — so conversions stay measurable on essentially any site. This is a concept and forward-roadmap piece, not yet built; the design draws directly on the dual-path Pixel + CAPI stack I shipped for Lustr.
What it's built with.
How it works.
Why a server-side path, not browser-only
A browser-only tag is the easy install, but it's lossy — ad blockers, iOS App Tracking Transparency, and privacy-strict browsers drop the request before it ever fires. On Lustr's Meta Pixel build I measured that gap at roughly 30–40% of conversions.
The low-friction install is still a snippet — the same mental model as the Meta or Google pixel — but it can't stand alone. Pairing it with a server-side path trades a little install simplicity for measurement that actually survives client-side blocking.
Dual-path: browser + server, deduplicated
The design is a dual-path stack: the browser snippet fires the event, and a server-side Conversions API fires the same event independently, the two tied together by a shared deduplication event_id so each real conversion is counted exactly once.
The server path can't be blocked by a client-side ad blocker, so it recovers the events the browser would have lost — without double-counting the ones it didn't. It's the same pattern I built end to end for Lustr, generalized into a reusable measurement layer.
The things I'm proudest of.
- ▹Browser-side snippet: a small JS tag dropped on a business's landing and checkout pages, firing a standard event taxonomy (Landing, Lead, Booking, Purchase, Call) keyed to a first-party attribution token.
- ▹Server-side Conversions API: a companion server-side path mirrors the key revenue events with a shared deduplication event_id, recovering the conversions that browser-only tracking loses to ad blockers, iOS ATT, and strict browsers — the same 30–40% gap I measured on Lustr's Meta Pixel + CAPI build.
- ▹No-code install targets: planned plugins for common stacks (Shopify, WordPress, Calendly, Stripe, GTM) so a non-technical owner can adopt measurement without a developer.
- ▹First-party by design: events are keyed to a first-party token and sent to infrastructure you control, rather than handed to a third-party ad network.