Segment Event Forwarding
Send one clean stream of product events to Segment and let it fan out downstream.
What it adds
A documented event schema and a single forwarding path emitting track, identify, group, and page calls with consistent identity.
What your agent is told to do
5
What your agent is told to do
5-
1
Write the event schema before writing any code: the exact set of event names, the properties each carries with their types, and the traits attached to a user and to an account. Every downstream tool inherits this schema, so a name chosen carelessly is expensive to change later.
-
2
Establish one identity model and apply it everywhere. Use a stable internal user identifier that never changes, associate the anonymous identifier from the first visit with it at signup, and attach the account or workspace so downstream tools can roll events up by customer.
-
3
Route every event through one internal emitter rather than calling the provider from feature code. That emitter validates the event against the schema, drops or flags anything unrecognised, and is the single place where identity and default properties are attached.
-
4
Assign each event a single origin, browser or server, and document it in the schema. Prefer the server for anything that must be accurate — purchases, plan changes, provisioning — and leave the browser for interactions only it can see.
-
5
Since Segment fans out to marketing and support tools, treat every property as though a downstream operator will read it. Never send credentials, payment details, message contents, or anything a user typed that was not intended for analysis, and honour the app's existing consent handling before emitting.
Edge cases it handles
8
Edge cases it handles
8- Without a fixed track, identify, group, and page schema, event names drift into near-duplicates and every downstream report has to be rebuilt. Keep the schema in version control, validate against it at emit time, and treat a new event name as a deliberate change.
- The same event emitted from both the browser and the server is counted twice in every destination it reaches, and the two copies will carry different identity. Declare one origin per event and enforce it in the emitter.
- Consent settings and per-destination rules are configured in the provider's workspace and in the app, and the two must agree. Do not emit before consent is resolved on the assumption that a downstream filter will catch it.
- Traits and properties travel further than the analytics warehouse — into email tools, support consoles, and advertising platforms. Restrict them to an allowed list and keep sensitive values out entirely.
- Delivery retries must not change an event's identity or its recorded timestamp. Set the timestamp at the moment the event occurred, carry a stable message identifier so a redelivery is deduplicated, and do not renumber or reorder a queued batch on retry.
- Ordering is not guaranteed end to end. An event referring to an entity must carry enough context to stand alone, because the identify or group call establishing that entity may arrive after it.
- An anonymous session that is never linked to a signup leaves the pre-signup activity stranded. Perform the alias or association at the moment of account creation, not later.
- When the provider is unavailable, buffer with a bounded queue and back off with jitter. Analytics delivery must never block a user request, and dropped events should be counted so the loss is visible.
Definition of done
9
Definition of done
9- A versioned event schema defines every event name, property, and trait, and the emitter validates against it.
- All events leave through a single internal emitter rather than direct calls from feature code.
- Each event has one declared origin and is never sent from both the browser and the server.
- Identity is consistent: a stable internal user identifier, the anonymous identifier associated at signup, and the account attached to every event.
- No credential, payment detail, or sensitive user content appears in any property or trait.
- Retried deliveries carry the original timestamp and a stable message identifier, and are deduplicated downstream.
- Consent is resolved before emission, and a provider outage degrades to a bounded buffer with visible dropped-event counts.
- 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
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
Data Table Cell Primitives
Data Table Cell Primitives
Render every kind of table cell the same way, wherever the table happens to be.
What it does
A shared set of cell renderers for numbers, dates, people, statuses, links, and row actions, used by every table in the app.
How it works
- 1 Catalogue the cell types the app's tables already render and reduce them to a small set: number and currency, date and relative time, person or avatar, status or badge, link or identifier, and an actions cell.
- 2 Separate each cell's underlying value from its presentation, so sorting, filtering, grouping, and export operate on the raw value while the user sees the formatted one.
- 3 Align and format numerically consistent cells the same way everywhere — figures right-aligned with tabular figures and a fixed precision per column, dates in the user's locale and time zone, currency with its code where more than one is possible.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/data-table-cell-primitives
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.