AI-first tag manager

One snippet. Every platform. Every conversion counted once.

Track collects your website events first-party, checks consent before anything leaves your site and delivers them server-side to Meta, Google, TikTok, LinkedIn and more — deduplicated, explained, and set up together with Track AI.

We only check the format here. Next, we create your site with a six-character tracking ID and guide you through the setup in chat.

  • EU data region
  • Consent checked before delivery
  • Signed, versioned configs
  • No custom HTML or JavaScript
See how it works

Interactive product demo

Interactive demoSample data

Accepted

6

Delivered

4

Duplicates removed

1

Tracking Health Score

Needs attention

70of 100

Path of the latest event: website → Track → consent check → destinations.

Latest events

  1. PurchaseBrowserDuplicate
  2. PurchaseServerHeld
  3. BeginCheckoutBrowserDelivered

Recommendation: 1 Purchase is held without a currency

Compact demo: the same sample data with fewer rows.

What you get

Three things your tracking should do — and usually doesn't

Pixels alone lose events, server-side setups need engineers, and consent is often a banner instead of a rule. Track turns all three into one guided setup.

  1. 01

    Every conversion counted once

    Browser and server send the same event ID; Track merges the pair and forwards one conversion per order. Replays never create a second one.

    In the demo: the dedup marker in the live event stream

  2. 02

    Only what consent allows leaves your site

    Each event passes a policy check before delivery. A denied consent blocks the destination, a missing decision never becomes a yes, and every decision is recorded with its reason.

    In the demo: the block reason on every held event

  3. 03

    You always know what to fix next

    A tracking health score with explainable parts and Track AI recommendations that point to the exact event and parameter — with a draft you approve.

    In the demo: the Purchase that arrives without a currency

How it works

Snippet → Track → Platforms

One asynchronous script on your pages, one router in the EU that checks consent and merges duplicates, and every destination fed server-side from the same verified event.

  1. 1

    Install one snippet

    Add the asynchronous tracker with your six-character site ID. It loads a signed configuration, never blocks rendering and fails safe if anything is wrong.

  2. 2

    Track checks and routes

    Events are validated, matched to their consent decision, deduplicated by event ID and order ID, then queued for each destination separately.

  3. 3

    Platforms receive verified events

    Meta, Google, TikTok, LinkedIn, Reddit and more get browser and server events with shared IDs; you see the delivery status and the last response per destination.

  4. Read the full walkthrough
Website → Track → Consent / policy → Destinations: the path every event takes.Your websitetracker.jsTrackEUConsent / policyMeta AdsGoogle AdsTikTok AdsLinkedIn AdsReddit Ads
Website → Track → Consent / policy → Destinations: the path every event takes.

The snippet

html
<script async src="https://cdn.track.site/v1/tracker.js" data-site-id="TRACKING_ID"></script>

Guided setup

Set up with Track AI. Publish only what you approve.

Track AI detects your platform, proposes a measurement plan and connects destinations with validated inputs. Every change becomes a draft with a readable diff — nothing goes live until you confirm.

  • Detects your CMS or shop system and the events that matter for it
  • Asks one question at a time; credentials go into secure cards, never into the chat
  • Every change is a draft with a diff, an approval button and one-click rollback
How Track AI works
Track AIExample conversation (static)
  1. I checked demo-shop.example and detected Shopware 6. Purchase events arrive with a value but without a currency, so Meta and TikTok cannot count revenue.

  2. Use EUR as the default.

  3. The change is ready for your review. Nothing changes until you confirm.

Draft v15 — review before publishing

+ purchase.currency: default EUR when the shop sends none+ destinations.meta.value_currency: EUR= 1 held Purchase event would be delivered
Static example with sample data. In your workspace the same flow runs against your real configuration and asks for your confirmation before publishing.

Use cases

Built for shops, lead generation and agencies

The same router with a measurement plan that fits your business.

E-commerce

Verified orders instead of browser guesses.

  • Purchase, refund and subscription events from Shopify, WooCommerce or Shopware webhooks
  • Order ID as the source of truth for deduplication
  • Value and currency validated before delivery

Lead generation

Every qualified lead attributed, none counted twice.

  • Lead events from forms and server with a shared event ID
  • Click IDs such as gclid and li_fat_id forwarded only with consent
  • Offline conversions uploaded when the deal is won

Agencies

Many sites, one workflow.

  • Several sites and brands per workspace
  • Drafts, approvals and an audit log for every change
  • Tracking health per client without opening five dashboards

Consent, security, EU data

Privacy is enforced in code, not promised in a banner

Track is built as a data, consent and routing layer. These are product facts you can verify in the documentation and the data processing agreement.

Consent
Strict opt-in defaults; a missing decision never becomes a yes
Consent Mode v2, TCF 2.2, GPP and GPC signals plus the common CMPs
Server-side delivery never bypasses a denied consent
Security
Signed, versioned configurations verified in the browser
Credentials envelope-encrypted; secrets never reach chat, logs or the model
Row-level security isolates every workspace in the database
EU data
Processing in the EU data region by default
Processor under Art. 28 GDPR with a data processing agreement
No fingerprinting, no consent bypass, no synthetic conversions

Tracking Knowledge

Learn how tracking really works

Guides on server-side tracking, deduplication and consent — written by the team building Track.

All articles

Pricing

Plans that grow with your event volume

Every plan includes browser and server-side tracking, all standard destinations, Track AI and the consent engine. Monthly billing is the default; a year costs ten monthly instalments.

  • Starter

    A single website, a small shop or the first professional tracking setup

    €19per month

    • 500,000 accepted events per month
    • 1 production website
  • Growth

    Recommended

    Growing shops and marketing teams with several sites

    €90per month

    • 5,000,000 accepted events per month
    • 5 production websites
  • Pro

    Agencies, larger shops, several brands and high volumes

    €180per month

    • 20,000,000 accepted events per month
    • 25 production websites

Enterprise · Custom

Custom volumes, infrastructure, governance and SLA

Talk to sales

14-day Growth trial, no credit card, no automatic conversion into a paid plan.

Net list prices in EUR; VAT is added where applicable.

Compare all plans

Ready for verified events?

Create your site, paste the snippet and let Track AI guide the rest. No credit card needed to start.