Cohort Analysis
Group users by when they started and watch how each group behaves over time.
What it adds
A retention grid that buckets users by a qualifying moment and tracks what each bucket does in the periods that follow.
What your agent is told to do
5
What your agent is told to do
5-
1
Define the qualifying event that puts a user in a cohort, and freeze their membership at that moment. A cohort that re-sorts itself as users change is not a cohort.
-
2
Support both calendar buckets (users who signed up in March) and rolling buckets (day 0, day 7, day 30 relative to each user's own start).
-
3
Render the result as a triangular grid: cohorts down, periods across, with each cell showing both the count and the rate.
-
4
Read from the app's existing event stream. Event capture is owned by Event Tracking — extend that rather than instrumenting a second pipeline.
-
5
Do NOT restate ordered step-conversion logic here; that belongs to Funnel Analytics. This feature is about time, not sequence.
Edge cases it handles
6
Edge cases it handles
6- A user who qualifies twice must be handled by a stated rule — first qualification only, or a separate row per qualification. Silently double-counting inflates every cell.
- The most recent cohort has not lived through a full period. Mark partial periods rather than plotting them as a collapse in retention.
- Late-arriving events change historical cells. Decide whether cells are recomputed or frozen, and say which on the page.
- Calendar buckets need a stated time zone. UTC and the viewer's local zone put the same user in different months.
- A cohort with a handful of users produces meaningless percentages. Suppress or flag rates below a minimum cohort size.
- Deleted or merged accounts must not silently shrink historical cohorts — retention would appear to improve.
Definition of done
8
Definition of done
8- Cohort membership is fixed at the qualifying moment and does not change retroactively.
- Both calendar and rolling bucketing are available and clearly labelled.
- Users who qualify more than once are handled by a documented rule.
- Partial and incomplete periods are visibly marked, not plotted as data.
- Small cohorts are flagged or suppressed rather than shown as noisy percentages.
- The bucketing time zone is stated on the report.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
UI Event Naming Schema
UI Event Naming Schema
Give every tracked interaction a name that still means the same thing in a year.
What it does
A documented vocabulary and structure for event names and properties, applied across the app's existing tracking.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ui-event-naming-schema
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
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.