Track
Start free

How it works

From your domain to verified conversions on every platform

One snippet on your site, one guided session with the assistant, one signed configuration you approve. Track takes the events from there — with consent evaluated for every destination and a debugger that shows you what happened.

Start with your domainSee the features
Snippet → Track → platformsThe snippet on your website sends events from the browser; your shop or server sends the same conversions with a shared event id. Track evaluates consent at a policy gate and forwards each event to Meta, Google Ads, Google Analytics 4 and TikTok.Websiteone event idBrowser SDKServer APITrack✓Consent / Policyconsent grantedMetadeliveredGoogle AdsdeliveredGA4deliveredTikTokdelivered
Snippet → Track → Consent/Policy → platforms. The same picture you see in the debugger for every real event.

Four milestones, one session

This is the customer's view. The technical checks behind each milestone are listed further down.

  1. Create your site

    Sign up with your domain. Track creates the site, a public six-character tracking id and the one-line snippet.

    You
    enter the domain and paste the snippet — or install the Shopify, WooCommerce or Shopware app
    You get
    a verified installation: Track sees the first page view and confirms ownership by DNS, file or meta tag
    The snippethtml
    <script async src="https://cdn.track.site/v1/tracker.js" data-site-id="TRACKING_ID"></script>

    Served from a first-party CDN host; the configuration it loads is Ed25519-signed and verified before anything runs.

  2. Let the assistant propose the setup

    The assistant detects platform and consent tool, proposes an event plan for your business type and asks for the public ids of the platforms you use.

    You
    answer a few questions and enter pixel ids in chat, access tokens in the vault card
    You get
    a drafted configuration with mapped events and a real test event accepted by the vendor

    Guided setup

    Example data: Static example state — not live traffic, no real customer data.

    1. Track AI

      example-shop.test runs on Shopify with Cookiebot as consent tool (high confidence). For a shop I suggest view_item, add_to_cart, begin_checkout and purchase. Shall I draft the plan for Meta and Google Ads?

    2. You

      Yes, Meta first.

    3. Track AI

      Pixel id validated. The Conversions API needs an access token — please enter it in the vault card below; it never appears in this chat.

    Vault card · Meta access token

    Stored encrypted; visible to no one, including the model.

    stored

    Test event · purchase

    Sent through the real pipeline with the vendor's test event code.

    accepted by Meta

    Publish version 13

    Bound to exactly this diff and to you as the approver.

    waiting for your approval
    • + destination meta: browser + server
    • + mapping purchase → Purchase (event id, order id)
    • ~ consent: marketing required for meta
    Approve and publish

    The assistant proposes, tools validate, you approve.

  3. Approve and publish

    You see the diff, the recipients and the consent requirement of every destination. One approval publishes a signed, versioned bundle.

    You
    read the diff and click approve
    You get
    a live configuration with its version number, rollback available with one click

    Configuration · version 13

    Example data: Static example state — not live traffic, no real customer data.
    live
    Approved by
    you, bound to the diff you read
    Signature
    Ed25519, verified by the SDK
    Destinations
    Meta (browser + server), Google Ads (server)
    Rollback
    version 12, one click

  4. Watch and improve

    The debugger shows every event with its decision, the health score reports what to fix, and the assistant proposes the fix.

    You
    check the score when it changes; approve improvements
    You get
    verified conversions on every platform, with evidence per event

    Tracking health

    Example data: Static example state — not live traffic, no real customer data.

    Score

    86 / 100

    Components

    • Consent coverage91 · 20% weight

      91% of events carry an explicit consent signal

    • Critical events78 · 25% weight

      7 of 9 planned critical events observed

    • Schema quality74 · 15% weight

      74% of events pass schema and PII checks

    • Duplicates96 · 10% weight

      1.0% duplicates

    • Delivery88 · 20% weight

      94% delivered, 1 integration with credential problems

    • Freshness100 · 10% weight

      Last browser event 4 min ago

    Open issues

    • purchase without currency

      12 events in the last 24 h are missing the required parameter

      Fix: update the event mapping
    • Consent signal missing

      9% of events arrived without an explicit consent state

      Fix: connect the CMP adapter

    Weighted components; a lower score always points at its cause.

Where your events come from

Switch between the delivery modes. Every destination can run browser-only, server-only or both; the hybrid mode is the default because the two paths cover each other's gaps.

Both paths, one event id

Browser and server send the same conversion with the same event id. Track normalizes both, applies the consent decision per destination and forwards them; the vendors deduplicate on the event id or the order id. You get the reach of the server path with the match quality of the browser path.

  • Default mode for every destination that supports both
  • Deduplication: event id (Meta, TikTok, Pinterest, Snapchat, Microsoft, LinkedIn …), order id (Google Ads)
  • Consent: one decision per event and destination for both paths
Both paths, one event idThe website sends events from the browser SDK and the server API with one shared event id to Track; the consent gate is open and events reach the destinations.Websiteone event idBrowser SDKServer APITrack✓Consent / Policyconsent grantedMetadeliveredGoogle AdsdeliveredGA4deliveredTikTokdelivered

What Track checks along the way

Show the technical checks behind the four milestones

These checks run inside the guided session and later in the worker. They are the reason the four milestones are enough — you do not have to verify them by hand.

Site and installation

  • Domain format and reachability
  • Ownership by DNS record, verification file or meta tag
  • Snippet present and configuration signature verified in the browser
  • First page view received on the ingest host

Platform, consent tool and event plan

  • Shop or CMS platform detected with a confidence level
  • Consent tool detected (TCF 2.2, GPP, Cookiebot, OneTrust, Usercentrics or consent API)
  • Event plan template chosen for the business type (shop, lead generation, SaaS, publisher)
  • Required parameters per standard event, naming rules for custom events, PII blocked in properties

Destinations and credentials

  • Public ids validated against the vendor's format
  • Access tokens stored in the vault via card or OAuth; never in the transcript
  • Consent purpose required by each destination recorded
  • Click-id matrix checked: every id forwarded only to its platform

Test, review and publish

  • Test event sent through the real queue and worker; vendor verdict recorded
  • Diff, recipient list and approver bound to one approval token
  • Bundle signed with Ed25519, versioned and immutable
  • Audit entry for every tool call and every approval

After go-live

  • Health score: consent coverage, critical events, schema quality, duplicates, delivery, freshness
  • Retries with backoff, circuit breaker and dead-letter queue per destination
  • Issues grouped by fingerprint, each naming the tool that fixes it
  • Rollback to any earlier version

Two planes, one signed configuration

A control plane for people and the assistant, a data plane for events. They share nothing but the signed configuration — a technical proof after the milestones, not a prerequisite for using Track.

Two planes, one signed configuration
ComponentResponsibility
Browser SDKConsent-gated storage, CMP adapters, batching transport, SPA tracking, vendor loaders with shared dedup ids. Kept under 30 KB gzip by a CI budget.
CollectorOrigin allow-list, rate limits, HMAC-signed server requests, kill switches, durable queue hand-off before the 202 is returned.
WorkerNormalization, PII scan, consent policy, event store, conversion dedup, usage ledger, fan-out, delivery with retries and DLQ.
Control planeDashboard and assistant: typed tools, approvals, audit log, RBAC, billing, privacy center — separated from the data plane.

Questions

Do I need a tag manager?
No. The tracker loads vendor tags itself after consent. Existing GTM setups can coexist during migration.
Where is data processed?
In the EU. Vendor APIs receive only what you configured, under the documented transfer basis shown for each destination.
How is the configuration protected?
Bundles are immutable, versioned and Ed25519-signed; the SDK verifies the signature before applying any configuration.
What if the AI provider is unavailable?
The same setup states are available as a rule-based wizard. Nothing in the pipeline depends on a model being online.

Ready when you are

Create your site, paste the snippet and let the assistant configure the first destination.

Start freeRead the docs