Does my tracking plan leave the browser?

Not until you choose to run a metered lane. The linter runs entirely in your browser and nothing you paste is uploaded until you press Run this lane. Files you drop or choose are read locally too.

What shapes of tracking plan can it read?

Paste the plan in whatever shape you have it - a markdown table out of a doc, a CSV from a spreadsheet, a JSON event schema, or the analytics.track calls themselves. TSV and semicolon-delimited exports and posthog.capture, gtag, mixpanel.track and amplitude.track code all parse as well.

What are the four lanes?

Audit the plan scores naming, properties, privacy, coverage and governance and ranks what to fix first. Standardise the taxonomy settles one convention and returns a rename list, a property dictionary and a deprecation plan. Build the metric tree turns the events into metrics with explicit formulas, guardrails and the decision each one supports. Write the implementation spec produces the ordered track, identify, page and group calls with typed payloads and a QA checklist.

Am I charged for a run that fails?

A run that never reached the model costs nothing, and a retry reuses the same idempotency key so a network blip cannot bill twice. If the model replies in the wrong format the app says so before spending the one extra run it needs to ask again.

Which analytics destinations does it target?

Google Analytics 4, Segment, PostHog, Amplitude and Mixpanel, or several at once if the choice is not made yet. The destination is checked against GA4 hard limits during the free lint and it decides the shape of the target-state artifact the taxonomy lane exports.

From the free check: the prescan as Markdown, the normalized plan as CSV, the prescan flags as CSV and a JSON Schema per event. From a run: findings, the area scorecard, the quick wins, renames, the property dictionary, deprecations, the metric tree as CSV, the destination-shaped target-state schema, the Analytics.js calls, and the whole result as Markdown or JSON.

Your tracking plan, checked before engineering builds it

Paste the plan in whatever shape you have it — a markdown table out of a doc, a CSV from a spreadsheet, a JSON event schema, or the analytics.track calls themselves. The browser reads every event and property and lints them for free. Then pick a lane.

Both examples ship with a saved model run for every lane, so you can see all four outputs without signing in and without spending a credit.

Your tracking plan nothing pasted yet

or drop a .csv, .tsv, .md, .json, .txt or .js file anywhere in this box — it never leaves your browser.

Primary destination

Naming convention to hold you to

The questions this plan has to answer

Used by the metric-tree lane to decide what the plan is actually for. Optional everywhere else.

Anything else worth knowing

Paste a plan to price the run.

Result

Findings

id	sev	area	finding	fix

The convention

Renames

from	to	why

Property dictionary

property	type	meaning	required on	example

Deprecations

What the model did with the free check

Assumptions and open questions

Next step

Raw model reply

The reply could not be parsed into the render contract, so it is shown as it arrived.

Your tracking plan, checked before engineering builds it

Free in-browser check

Working

Result

Findings

Area scorecard

Quick wins

The convention

Renames

Property dictionary

Deprecations

Metric tree

Blind spots

Identity model

Calls, in the order they fire

QA checklist

What the model did with the free check

Assumptions and open questions

Next step

Raw model reply

Recent runs

If the run failed