After the map exists

Event taxonomy rewrite

Taxonomy work is unglamorous on purpose. It is the difference between `btn_click_2`, `CTA_tap`, and `checkout_started` all meaning the same human action, and a single name that still makes sense after the button colour changes.

Printed plans and notes spread on a desk

Who it is for

Teams who already have an instrumentation audit, or a long event export, and who can see that the same action lives under three names.

What you receive

A proposed taxonomy with old-to-new mappings, retirement notes for duplicate events, and a suggested order for changing them in upcoming versions.

Scope

The event set of one product, based on an existing audit or a complete event export you provide.

What we refuse to do

We will not add a prefix to every event and call it a system. Names follow the user's action. Parameters carry the screen, the variant, and the result. If a name only makes sense to the intern who added it during a hack week, it is a candidate for retirement.

How it lands in the app

The mapping table is ordered so you can change the noisiest duplicates first. We do not require a big-bang rename in a single version. Historical charts will break where names change; we note that in the walkthrough rather than pretending otherwise.

Included

  • Review of current names, parameters, and known duplicates
  • Proposed naming convention with examples from your screens
  • Old-to-new mapping table
  • Retirement notes for events that should stop firing
  • Sixty-minute walkthrough of the mapping

Not included

  • A fresh instrumentation audit (commission that separately if you do not have one)
  • Changing names inside the live analytics property on your behalf
  • Historical data backfill

How the work proceeds

  1. Source

    We take the audit report or the export, plus a list of screens that have moved since.

  2. Draft mapping

    We group events by user action, not by the team that added them.

  3. Walkthrough

    Engineering and product mark which renames can land in the next version and which must wait.

Preparation

An audit from us, or a full event export plus screen recordings of the main journeys.

Constraints

We will not invent a taxonomy for a product we cannot see. Incomplete exports produce incomplete mappings.