Interaction Telemetry Guardrails
Collect useful interaction signal without recording what people type or read.
What it adds
Redaction, sampling, and consent rules applied to interaction events before they leave the browser.
What your agent is told to do
5
What your agent is told to do
5-
1
Set the default to sending no content. An event records that a thing was interacted with, its type and its identifier; it does not record the text inside it unless that field is explicitly listed as safe.
-
2
Redact at the point of collection rather than after ingestion. Once a customer's message body reaches the analytics vendor, deleting it is a support request to a third party and a disclosure you have already made.
-
3
Sample the high-frequency signals — scrolling, hovering, typing, resizing — at a rate recorded on the event itself, so the numbers can be scaled back up correctly instead of being read as raw counts.
-
4
Honour the user's consent choice and the workspace's privacy configuration before anything is queued, and drop the queue when consent is withdrawn rather than sending what was already collected.
-
5
Distinguish an action a person took from a change the interface made. Restored scroll positions, programmatic focus, prefetches, retries, and automated tests all produce interaction-shaped events that are not interactions.
Edge cases it handles
7
Edge cases it handles
7- Private content leaks through the least obvious properties: a page title containing a customer name, a URL path with an email in it, a form label carrying a filename. Redaction must cover titles, paths, labels, and error text, not only field values.
- High-frequency events dominate the volume and the cost while carrying little information per event. Sample them, and record the sampling rate on the event so nobody later reports a tenth of the real number as fact.
- Consent and workspace privacy settings are checked before an event is queued, not before it is sent. A queue built up in advance and flushed after a refusal is exactly the outcome consent was supposed to prevent.
- Events generated by the app rather than the user — restored state, automated retries, synthetic monitoring, test runs — must be excluded or clearly marked, or engagement metrics will measure the software's own behaviour.
- The volume of events must be bounded so a stuck component cannot flood the queue and the network from a single session.
- Some jurisdictions and enterprise workspaces require regional storage or complete opt-out, so the destination and the ability to send nothing at all must both be configurable.
- A retention period has to be set deliberately for interaction data, because the default in most tools is longer than any legitimate use of it.
Definition of done
9
Definition of done
9- Events carry no user-entered text, and safe fields are enumerated explicitly rather than assumed.
- Redaction happens in the browser before any event is transmitted.
- High-frequency events are sampled and each event states the rate it was sampled at.
- Consent and workspace privacy are evaluated before an event is queued, and withdrawal drops the pending queue.
- App-generated interactions are excluded or distinctly marked.
- Per-session event volume is capped.
- Destination region, opt-out, and retention period are configurable and documented.
- 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.