Revenue values on goals

What it is

The optional events.js add-on already sends a name and an optional label. You can now also send a numeric value. The collector stores that number on the same custom event row, and each event, click or form goal shows the sum for the date range. Unique visitor counts and the funnel are unchanged. This is separate from Stripe revenue and the conversions API, which keep their own currency totals. script.js stays 845 B.

Why it matters

A goal is more useful when it can show how much those conversions added up to, without turning quietstats into an ecommerce tracker.

How it works

1. Install the optional events script, the same way you already do for custom events.
2. Call qs('Purchase', 'pro', 49), or put data-qs-event, data-qs-prop and data-qs-value on a button.
3. Add an event goal for Purchase (or a click or form goal). The Goals card shows the summed value next to the visitor count.

Privacy: what is and isn’t collected

Collected

• The same event name, optional label and path you already send
• An optional number (0 or more, up to 1 billion, two decimal places)

Never collected

• Order IDs, invoice numbers or customer references
• A currency code — this is a unitless sum on the goal, not mixed with Stripe totals
• Anything typed in a form
• Cookies, localStorage or anything else stored on the visitor’s device
• IP addresses or user agents (used in memory, then discarded)
• Anything that links a visitor across days (the visitor ID resets daily)

How quietstats works, and the legal caveats →

Rows and limits

• One optional number on the same custom event row (migration 0052, additive)
• Invalid, negative or huge values are dropped; the event is still counted
• Core script.js is unchanged (845 B); events.js stays under 2.5 KB
• Stripe Payment Links and the conversions API are unchanged

“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →