Features
Server-side event router
Send each conversion once and let every platform receive it in the way it counts best — browser, server or both — without double counting.
Destination health
Example data: Static example state — not live traffic, no real customer data.| Destination | Mode | Health | Last delivery | Queue |
|---|---|---|---|---|
| Meta | browser + server | healthy | 12 s ago | 0 retries |
| Google Ads | server | healthy | 40 s ago | 0 retries |
| TikTok | browser + server | degraded, circuit breaker open | 6 min ago | 3 in dead-letter queue |
| server | paused by kill switch | 2 h ago | held |
Health, mode and queue per destination; failures are handled, not hidden.
Example destination health: two healthy destinations, one vendor outage handled by the circuit breaker, one destination paused by a kill switch.
Browser and server share one event id
Track receives events from the browser SDK, your server, shop platforms and affiliate networks, normalizes them into one schema, applies consent, and routes them to 22 destination types with retries, circuit breakers, a dead-letter queue and replay.
The browser SDK and your server (or shop webhook) send the same purchase with the same event id. Track normalizes both, evaluates consent per destination and forwards them; Meta, TikTok, Pinterest, Snapchat, Microsoft, LinkedIn and the others deduplicate on that id, Google Ads on the order id.
How it is built
The technical decisions behind the capability — the proof after the benefit.
01
Hybrid by default
Every destination can run browser tag, server API or both. Both paths share one event id, so Meta, TikTok, Pinterest, Snapchat, Microsoft, LinkedIn and the others deduplicate reliably.
02
Durable and observable
A durable queue with idempotent messages, per-destination retries with jittered backoff, circuit breakers on failing vendors, dead-letter storage and replay. Every attempt is recorded with a redacted payload preview.
03
First-party by design
The tracker is served from your CDN host, events go to your ingest host, configuration bundles are Ed25519-signed and verified in the browser before anything loads.
Browser-only tags versus the hybrid router
Why one event through Track is worth more than the same pixel fired twice.
| Browser-only tags versus the hybrid router | Browser-only tags | Browser + server with Track |
|---|---|---|
| Lost events | Blocked scripts and closed tabs simply drop the conversion | The server path still delivers it; the browser path adds match data when available |
| Duplicates | Pixel and server API count the same order twice | Shared event id and order id; vendors deduplicate |
| Vendor outage | Silent failure, no retry | Retries with backoff, circuit breaker, dead-letter queue and replay |
| Where data goes | Third-party endpoints called from the page | First-party ingest host; vendors receive only mapped fields |
What you can verify
Product facts you will find in the dashboard, the docs and the audit log.
- Browser SDK kept under 30 KB gzip by a CI budget, with consent-gated storage
- Server API with source keys for CRM and offline conversions
- Kill switches per site and organization
- EU data plane with row-level tenant isolation
Questions
- Does server-side tracking bypass consent?
- No. Consent is evaluated for every event and destination; without the required purpose nothing is stored, sent or replayed later.
- What happens when a vendor is down?
- Deliveries are retried with backoff, the circuit breaker pauses the destination, failed events land in the dead-letter queue and can be replayed once the vendor recovers.
More capabilities
Built on the same signed configuration and event schema.
- AI-guided setup
Describe your site, confirm each step, publish a signed configuration.
- Event debugger and lineage
See every event with its consent snapshot, routing decision and vendor response.
- Data quality and health score
A single score with explainable components and issues that link to their fix.
- Consent-aware by construction
Strict opt-in defaults, Consent Mode v2, purpose-based destinations, no replay after consent.
- Click ids and attribution done right
Capture only the ids the destination needs, only with consent, only for the documented window.
Try it on your domain
Create a site, install one snippet and let the assistant configure the first destination in minutes.