Stop installing tags.
Plan them.
OnTracks crawls your site, drafts the events that matter to your funnel, writes the GTM container, then checks they fire on the live page. When a redesign breaks a tag, a re-scan shows you which one and proposes the fix. The 6-week tag project, in one afternoon.
You create an account, you paste a URL · free until you deploy, no card
Four steps.
Always in this order.
Web analytics has been stuck in the same loop for ten years. Tracking gets wired by hand, GTM in one tab and the site in another; six weeks later, a container ships with no record of what was decided. Then a theme update breaks the cart_view tag and nobody notices for a quarter. The problem was never the skill of whoever wires the tags: it is that they are asked to start over on every site. OnTracks replaces every step of that loop with a platform that does the work and shows you what it did, while it does it.
- 01
Crawl
— Look
OnTracks walks the site the way a real visitor sees it: cookie banners accepted, deferred content waited for, SPA routes followed. Every clickable, every form, every signal pinned with several redundant selectors — enough to hold when the theme changes.
- 02
Plan
— Reason
Crosses what the crawl brought back with your business context — what you actually sell, what to skip — and proposes a set of events you can defend in front of your client, line by line.
- 03
Deploy
— Ship
OnTracks writes the container straight into your GTM. Selectors become triggers, params become variables, and the critical events — purchase, lead — come with a server-side mapping to Meta and LinkedIn, ready for you to confirm before anything is sent.
- 04
Verify & watch
— Hold
A check re-tests your tags against the live page. When a redesign breaks one, a re-scan tells you which tag lost its anchor and proposes a new one. You approve; the plan is updated, and you redeploy the container when you're ready.
What lands on your desk
when the run is done.
Every artefact is versioned, queryable, and reversible. A v9 plan tracks what produced it. A rolled-back container can be redeployed in a single click. The platform is the audit trail.
- 01 /05
A tracking plan
Not a Notion doc. A schema-validated JSON: every event says why it exists, how well it will survive the next redesign, what volume to expect, and how it honors consent.
- 02 /05
A live GTM container
Pushed via the Google API. Versioned. Re-deployable. The container reflects the plan; the plan reflects the site.
- 03 /05
A configured GA4 property
Custom dimensions and conversion events are registered in your property, aligned with the plan. The container sends; GA4 knows what to do with it.
- 04 /05
Server-side conversions (CAPI)
Meta and LinkedIn. Personal data hashed before it leaves. Consent respected. No 1×1 pixel theater.
- 05 /05
A re-scan that finds your tags again
When the theme moves, the re-scan spots the selectors that no longer match and proposes a new anchor. Surfaces only what a human needs to confirm.
One setup fee.
One monthly event bracket.
Tiered by total active sites — the more you bring, the lower per-site.
By event volume; demos are free; you pay when you deploy live.
No seats. No event-type taxes. A platform-reliability guarantee covers the cases where OnTracks could fail you: a broken plan, an unhealthy container, a verification we can't reproduce, an event we can no longer anchor to your page.
Read the full pricing →The right tracking plan is specific to each business, and there is no reason a human should have to rediscover it from scratch on every new site.
Bring a URL.
Leave with a deployable plan.
Create your account, paste a URL, read the plan, then decide. Free until you deploy live: the setup fee is charged once, at that point. No card to start.