UI Event Naming Schema
Give every tracked interaction a name that still means the same thing in a year.
What it adds
A documented vocabulary and structure for event names and properties, applied across the app's existing tracking.
What your agent is told to do
5
What your agent is told to do
5-
1
Audit the events the app already sends and list them. The duplicates, the near-synonyms, and the ones nobody can explain are the reason the schema is needed, and they are also the migration list.
-
2
Fix a structure of object, action, and context: what was acted on, what happened to it, and where. Fix a closed set of actions — viewed, clicked, opened, submitted, selected, failed — and require every new event to reuse one of them.
-
3
Keep variable detail in properties, never in the name. A record identifier, a plan name, or a workspace slug baked into an event name produces thousands of unaggregatable one-off events.
-
4
Separate product events, which describe what a user achieved, from operational events, which describe how the interface behaved. They have different audiences, different retention, and often different destinations.
-
5
Version the schema and treat a change of meaning as a new name rather than a redefinition. A chart that silently changes what it counts halfway through is worse than one that visibly breaks.
Edge cases it handles
7
Edge cases it handles
7- Without a fixed object, action, and context structure, two teams will record the same interaction under three names and the numbers will never reconcile. The structure has to be enforced at the point events are declared, not agreed informally.
- Identifiers, search terms, and other variable values in event names create unbounded cardinality that no analytics tool can aggregate and every analytics bill will reflect. They belong in properties.
- A breaking change needs a new name and an overlap period where both are sent, so historical comparisons stay possible rather than showing a cliff on the day of the rename.
- Product and operational events must be distinguishable at a glance, because an operational event counted as product usage inflates engagement with things like retries and background refreshes.
- Property names and value shapes need the same discipline as event names; the same concept appearing as workspaceId in one event and workspace in another defeats every join.
- The schema must cover failures as first-class events, not just successes, or the funnel shows what worked and nothing about what did not.
- A deprecated name must remain documented after it stops being sent, so anyone reading an old dashboard can tell what it used to mean.
Definition of done
9
Definition of done
9- Every event in the app follows the documented object, action, and context structure.
- Actions come from a fixed, published list rather than being invented per screen.
- No event name contains an identifier, a search term, or any other variable value.
- Product and operational events are separated and labelled.
- Property names and value shapes are consistent across every event that carries them.
- Breaking changes ship as new names with a documented overlap period.
- The existing events that predated the schema have been migrated or explicitly deprecated in writing.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Amplitude Event Tracking
Amplitude Event Tracking
Send behavioural events to Amplitude with stable users, devices, and account grouping.
What it does
A server-side pipeline that forwards behavioural events, user properties, and account-level groupings to Amplitude.
How it works
- 1 Identify the behaviours worth measuring and emit them from one place in the application layer, so that the set of events is readable in a single file rather than inferred by grepping the codebase.
- 2 Establish the identity model before writing any send code: what identifies a signed-in user, what identifies a device or anonymous session, and how the two are stitched at sign-up and sign-in.
- 3 Map the app's own tenancy — workspace, organisation, or team — onto Amplitude's group concept, and derive it from the record the event belongs to rather than from whatever context the request happened to carry.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/amplitude-event-tracking
Component Analytics Hook
Component Analytics Hook
Instrument shared components once instead of hand-writing events on every screen.
What it does
Interaction tracking attached to the app's shared components, emitting named events carrying the context of where they were used.
How it works
- 1 Identify the shared components that account for most interaction — buttons, links, menus, dialogs, tabs, table rows, form submits — and attach tracking inside them rather than at each of the hundreds of call sites.
- 2 Have each component emit its own identity and the context it was rendered in: the screen, the surface, and a stable identifier supplied by the caller. Position on the page and visible label are not identity.
- 3 Emit exactly one event per user action. A menu item inside a card inside a table row must not produce three overlapping records of the same click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/component-analytics-hook
Mixpanel Event Tracking
Mixpanel Event Tracking
Send product events to Mixpanel with identities that survive sign-up and sign-in.
What it does
A server-side event pipeline that forwards named product events and user profile updates to Mixpanel, with a stable identity model.
How it works
- 1 Find every meaningful moment already recorded in the app — sign-up, activation, the core action, upgrade, cancellation — and route them through one tracking call site rather than scattering emits through controllers and views.
- 2 Define the event catalogue once, in code, as the only source of names and property types, and reject an event whose properties do not match the declared shape instead of sending it and discovering the drift in the dashboard six weeks later.
- 3 Emit from the server using the app's existing background-job system so tracking never blocks a request, and never ship the project credential into client-side code where anyone can read it and forge events.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mixpanel-event-tracking
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.