Plausible Goal Event
Record real conversions in Plausible without collecting anything that identifies a person.
What it adds
A small, fixed set of named goal events fired from confirmed outcomes, with low-cardinality properties and consent respected.
What your agent is told to do
5
What your agent is told to do
5-
1
List the outcomes that genuinely count as conversions — a completed signup, an activated workspace, a first successful action, a completed purchase — and give each one a short fixed name agreed up front. Keep the list small enough that someone can read it on one screen.
-
2
Fire each goal only after the outcome has actually succeeded and been committed, not when the user clicks the button that begins it. A goal fired on intent overstates every number that follows it.
-
3
Decide per goal whether it is sent from the browser or from the server and record that decision alongside the goal name. Sending the same conversion from both is the usual cause of doubled numbers.
-
4
Keep custom properties to a handful of low-cardinality values such as plan tier or source, and never attach an email address, a user identifier, a record identifier, or anything typed by a user. The point of this provider is that it does not build a profile of the visitor.
-
5
Route the sends through the app's existing consent or regional privacy handling rather than adding a second check. If the app has a separate brief for a fuller analytics pipeline, this entry owns only the named conversion goals and leaves general page and behaviour tracking to that one.
Edge cases it handles
8
Edge cases it handles
8- Goal names must be stable constants, because the provider treats a changed name as a new goal and the historical series simply stops. Never build a name from user content, a plan name that marketing can rename, or an identifier.
- The same conversion fired from the browser and again from the server doubles the count, and the two will disagree because one is blocked by ad blockers and the other is not. Pick one origin per goal and enforce it.
- Custom properties with unbounded values make the reports unusable and can carry personal data by accident. Restrict properties to an allowed key list with a known set of values.
- Consent and regional rules configured elsewhere in the app must gate these sends too. A goal that fires before the user has answered the consent prompt is a compliance problem regardless of how little data it carries.
- A goal fired optimistically before the transaction commits will count conversions that were rolled back. Send after commit, from the code path that knows the outcome succeeded.
- Client-side sends are blocked for a meaningful share of visitors, so browser-origin goals will always undercount. Note which goals are affected rather than treating the numbers as complete.
- When the provider is unreachable, the send must fail quietly. Analytics must never block a checkout, a signup, or any user-facing flow, and a failed send is not worth an error shown to the user.
- Retries on a fire-and-forget send create duplicates without improving accuracy. Either accept the loss or send server-side with a deduplication key, but do not blindly retry.
Definition of done
8
Definition of done
8- Every goal has a fixed name from an agreed list, with no dynamic or user-supplied content in it.
- Each goal has exactly one declared origin, browser or server, and is not sent from both.
- Goals fire only after the underlying outcome is committed and successful.
- Custom properties are restricted to an allowed low-cardinality set and contain no personal or identifying data.
- Consent and regional privacy settings gate every send through the app's existing handling.
- A provider outage or a blocked request never blocks, delays, or errors a user-facing flow.
- 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.