The pain

Event taxonomies rot the moment more than one team instruments. Product ships Button Clicked. Growth adds btn_click. An older funnel still fires button_clicked. Synonyms pile on — cta, signup, auth — and analytics charts splinter into parallel series that look different but mean the same thing.

The usual “fixes” are slow or unsafe. Waiting on eng for a rename pass takes a sprint. Pasting thousands of rows into a spreadsheet doesn’t cluster near-duplicates. Uploading an event export to another SaaS just to normalize casing is the wrong trade for sensitive product data. Meanwhile dashboards stay wrong, and governance docs drift further from production.

Who it’s for

Taxon is for people who own event-taxonomy hygiene but don’t want another vendor for a one-off cleanup:

  • Analytics / data folks cleaning an Amplitude, Mixpanel, or Heap export before a taxonomy review
  • Product managers who need a readable schema pack — or a shareable taxon-map.json — for the team wiki
  • Growth or lifecycle operators who inherited inconsistent naming across funnels
  • Anyone who has already tried “fix it in Sheets” and watched near-dupes survive

If the job is “make this CSV legible and leave with a canonical list,” Taxon is the tool. If the job is “rewrite production instrumentation across every client,” that’s still an eng project — Taxon gives you the map first.

What it does

  • Clean the export — drop or paste an Amplitude, Mixpanel, or Heap CSV; auto dialect + event column.
  • Merge with confidence — near-dup keys get a canonical name; clusters show shared vs differing properties; synonym tokens stay visible.
  • Decide per cluster — sticky Keep separate; Accept canonical writes into the pack / map; filter near-dups / low overlap / high volume.
  • Leave with artifacts — wiki taxon-pack.md, taxon-map.json, prior-schema diff, tracking-plan round trip.
  • Free · local-only — everything in the browser; CSV never uploads.

Same tool also normalizes casing/whitespace, clusters near-duplicate event names (synonym packs: Default / SaaS / Ecommerce), and exports cleaned CSV plus schema Markdown/JSON. No paywall. No feature tiers.

Why client-side

Event taxonomies are sensitive by default: they describe product behavior, experiments, and sometimes customer journeys. Taxon parses, clusters, previews, and exports in the browser. The CSV never uploads. There is no account wall to start. Marketing pages count anonymous pageviews only — file contents are never part of that signal. That is the product contract: make the messy legible without moving the pile.

A typical use

  1. Export events from Amplitude, Mixpanel, or Heap (or open a sample CSV in the app).
  2. Open Taxon, drop the file or paste rows. Confirm the detected dialect and event column. Pick a synonym pack if SaaS or Ecommerce naming fits.
  3. Scan clusters: exact matches collapse first; near-dups show synonym tokens that fired and which properties they share (e.g. btn_click → button_clicked). Filter near-dups only / low overlap / high volume when the list is long. Click a shared or differ prop for CSV examples.
  4. Finish the row: Accept canonical on clusters you trust; Keep separate on true outliers (sticky across re-normalize). On Properties, merge keys, set TYPE from examples, or Accept canonical — it writes into the pack.
  5. Download the cleaned CSV, taxon-map.json, and wiki taxon-pack.md — paste the pack into the team wiki without hand-edits (cluster decisions included).
  6. Optional: import a tracking plan, review matched / plan-only / CSV-only, export a patched plan — or load a prior schema and review full diff lists + export.

The output is something you can bring to a taxonomy review with a straight face — not a raw dump of every casing variant that ever shipped.

When NOT to use it

  • You need live Amplitude / Mixpanel / Heap API sync, auto-rename in production, or org-wide governance workflows — Taxon is a local cleaner, not an analytics platform.
  • Your “events” are not in a CSV/table form (screenshots, slide decks, verbal lists).
  • You want a hosted multiplayer taxonomy CMS with permissions and audit trails.
  • You need a multiplayer hosted taxonomy CMS with permissions and audit trails (Taxon is a local cleaner).

Prefer the duplicate-events pain page when the problem is already clear, or the naming-conventions page when you’re standardizing before the next instrument pass.