Revenue from Stripe Payment Links

What it is

Add /js/revenue.js next to your quietstats tag. On pages with buy.stripe.com links it adds a short source label (channel, source and landing page, such as AI · chatgpt.com · /pricing) to each link as Stripe’s client_reference_id. Stripe sends it back in a webhook when the payment completes, and quietstats adds the amount to that source’s daily total.

Why it matters

Visitors are only half the story. Knowing that ChatGPT brought five sales and a newsletter brought none is what tells you where to spend your time.

How it works

1. The label says where the visit came from, never who: no visitor ID, cookie or storage, and no customer or email is read from Stripe.
2. Each site has its own webhook endpoint, verified with that site’s Stripe signing secret, which is stored encrypted.
3. Repeated webhooks are counted once.
4. Stripe test mode only for now: live payments are refused until live mode is switched on.
5. It is optional and separate from the core script, which stays under 1 KB.

Set it up

<script data-host="https://quietstats.co.uk" data-site="YOUR_SITE_ID" src="https://quietstats.co.uk/js/revenue.js" async defer></script>

Replace YOUR_SITE_ID with the ID on your site’s settings page. Install guides →

Privacy: what is and isn’t collected

Collected

• Per day and source: number of sales and their total, in the payment currency

Never collected

• Customer names, emails or card details
• Order or payment IDs
• Any visitor ID
• 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

• About 1 KB extra, only on pages where you add it
• Rows: about 3 per sale (one total row, one de-duplication row, one setup row per site)

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