Conversions API for server-side sales

What it is

POST /api/v1/conversions with a “Send conversions” key that belongs to one site. Send the amount, currency and, optionally, the source label from /js/revenue.js or a source and landing page. The total is added to that day’s revenue for the source.

Why it matters

Not every sale goes through a Stripe Payment Link. The API lets any backend report revenue without adding tracking to your checkout pages.

How it works

1. Keys are scoped: a conversions key can send totals but can’t read any stats, and read keys can’t send.
2. Requests with personal data (email, visitor_id, user_id, customer, ip, name, phone, order IDs) are rejected with 422.
3. Send an Idempotency-Key header and retries are counted once.
4. Full reference: /docs/conversions-api.

Set it up

curl -X POST https://quietstats.co.uk/api/v1/conversions \
  -H "Authorization: Bearer qs_…" -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-2026-10-28-0042" \
  -d '{"amount": 49.00, "currency": "GBP", "source": "chatgpt.com", "landing": "/pricing"}'

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

Never collected

• Who bought: no email, customer, visitor or order 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

• Same hourly limits as the Stats API
• Days: today or up to 35 days back
• Rows: 1 to 2 per request

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