Mixpanel Event Tracking
Send product events to Mixpanel with identities that survive sign-up and sign-in.
What it adds
A server-side event pipeline that forwards named product events and user profile updates to Mixpanel, with a stable identity model.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Give every event a deterministic identifier derived from the record and action that produced it, so a job retried after a timeout produces the same identifier and the destination collapses the duplicate.
-
5
Decide once whether Mixpanel or Amplitude owns behavioural analytics. If Amplitude Event Tracking is also being applied, put the shared event catalogue and the identity resolution in one place and let each destination be a thin adapter over it, rather than maintaining two divergent lists of event names.
Edge cases it handles
8
Edge cases it handles
8- Event names and property types must stay stable once they are in use. Renaming an event or changing a property from a string to a number splits the history into two series and silently breaks every saved report built on it.
- Anonymous activity must be merged into the known user only when the app has real evidence they are the same person. Two people signing in from one shared browser must not have their pre-login behaviour joined onto whichever account authenticated first.
- Retries after a network timeout must not double-count. The send may have succeeded before the connection dropped, so identity of the event has to come from the app, not from the moment of transmission.
- Profile properties overwrite history; event properties do not. A value that describes the moment, such as the plan at the time of purchase, must be sent on the event, or a later upgrade will rewrite every past record to look like it always happened on the new plan.
- Regional data residency and consent settings must be honoured before the first event leaves the app. Sending to the wrong region, or sending at all for a user who declined analytics, is not something a later deletion request repairs.
- Rate limiting and outages must degrade quietly. Buffer, back off with jitter, and drop the oldest events once the buffer is full rather than growing it until the process runs out of memory.
- Personally identifying content — email bodies, message text, addresses, tokens — must never be attached as a property, even when it would be convenient for a funnel.
- The tracking pipeline must be disabled entirely in development, test, and preview environments, or staging noise will pollute production funnels.
Definition of done
9
Definition of done
9- Every tracked event is declared in a single catalogue and validated against it before sending.
- Anonymous sessions merge into the authenticated user without joining unrelated accounts on a shared device.
- A retried delivery produces one event in the destination, not two.
- Values that describe a point in time are carried as event properties and are not rewritten by later profile updates.
- Consent state and the configured region are respected before any event is transmitted.
- Credentials exist only on the server, and no analytics call blocks a user-facing request.
- A destination outage causes queued retries and eventual drops, never a failed user action.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Segment Event Forwarding
Segment Event Forwarding
Send one clean stream of product events to Segment and let it fan out downstream.
What it does
A documented event schema and a single forwarding path emitting track, identify, group, and page calls with consistent identity.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/segment-event-forwarding
Google Analytics Server Events
Google Analytics Server Events
Report confirmed outcomes to Google Analytics when browser tracking cannot be trusted.
What it does
Server-side delivery of completed conversions to Google Analytics, joined to the browser session and deduplicated against it.
How it works
- 1 Identify the outcomes the browser cannot see or reports unreliably — a payment confirmed by a webhook, a subscription that renewed, a signup completed after a redirect, anything blocked by an ad blocker — and send those from the server.
- 2 Capture the analytics client identifier from the browser when the visit begins, store it against the session or the record, and send it with the server event so the conversion joins the same session and campaign rather than appearing as a new anonymous visit.
- 3 Generate a stable event identifier at the moment the outcome happens and use it for both the browser and the server send, so the provider can collapse the pair into one event. Assign each event type a primary origin and treat the other as the fallback.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/google-analytics-server-events
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.