Amplitude Event Tracking
Send behavioural events to Amplitude with stable users, devices, and account grouping.
What it adds
A server-side pipeline that forwards behavioural events, user properties, and account-level groupings to Amplitude.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Send through the app's existing background-job system with a deterministic per-event identifier so retries, offline replays, and queue redeliveries collapse to a single recorded event.
-
5
This overlaps Mixpanel Event Tracking. If both are being applied, the event catalogue, the anonymous-to-known stitching, and the deduplication identifiers belong to a shared internal layer; only the transport, the group mapping, and the credential belong to this brief.
Edge cases it handles
8
Edge cases it handles
8- The transition from anonymous to authenticated must carry the earlier session forward exactly once. Stitching on every subsequent request re-attributes history repeatedly and inflates activation numbers.
- User properties describe the person now; event properties describe the moment. Sending the current plan as a user property and then reading it back as if it applied historically produces confidently wrong retention analysis.
- Group identifiers must come from the tenant that owns the record. Attaching a user's default workspace to an event that actually happened in another workspace makes per-account metrics untrustworthy in exactly the accounts that matter most.
- Server retries and any offline client queue can both replay the same event. Deduplication has to key on something the app generated at the moment of the action, not on arrival time or a sequence counter.
- High-cardinality properties such as raw IDs, full URLs with query strings, or free text will exhaust property limits and make charts unusable. Bucket them or leave them out.
- Sensitive fields must never travel as properties. Assume anything sent is retained beyond the app's own deletion process and cannot be recalled.
- When the destination rate-limits or returns errors, back off with jitter and cap the queue. An unbounded retry loop against a degraded endpoint will take down the worker pool that also runs email and billing jobs.
- A user who withdraws consent must stop generating events immediately, and the app needs a path to request deletion of what was already sent.
Definition of done
9
Definition of done
9- Events are emitted from one declared catalogue rather than ad hoc call sites.
- Anonymous and authenticated activity are stitched once per session transition, with no repeated re-attribution.
- Group identifiers always reflect the tenant that owns the underlying record.
- Duplicate deliveries from retries or offline replay resolve to a single event.
- No high-cardinality or sensitive value is sent as a property.
- Destination errors and rate limits produce bounded, backed-off retries that never fail the originating user action.
- Consent withdrawal halts transmission and is recorded so deletion can be requested.
- 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.