Know what sold, and what sold it.

Reporting that starts with the money

The dashboard overview shows gross volume, orders over time, customers, and subscriptions — and an attention list of the things that need someone: failed orders, past-due subscriptions, failing webhooks.

Underneath, the analytics API answers the deeper questions: revenue breakdowns, top products, customers, discount performance, the checkout conversion funnel, subscription movement, and a business summary. Orders export to CSV from the dashboard or the API.

Attribution on every order

When a checkout starts, Throttle records a clientContext for it: UTM parameters, Google and Meta click ids, analytics cookies, landing page, and referrer — merged with what the hosted checkout page sees, and stamped with the buyer’s IP and user agent on the server. It’s stored on the order and included in the order.created webhook, so every downstream tool knows where the sale came from.

Purchases your ad platforms can trust

• Server-side events. Purchases go to Google Analytics 4 through the Measurement Protocol and to Meta through the Conversions API — fired when the payment actually happens, not when a thank-you page loads.
• Hosted pixels. On hosted checkout, Throttle loads your GA4 and Meta tags for you.
• No double counting. Events are deduplicated by order id, and subscription renewals aren’t reported as new purchases.
• Consent respected. Events can require consent, with separate analytics and marketing consent.

Ask instead of build

Every one of these reports is also available to an AI assistant — ask Claude for last month’s revenue by channel instead of building the chart.

Good to know

• Funnel, product, and revenue breakdowns are available through the API and AI assistant; the dashboard shows the overview.
• CSV export covers orders.
• Throttle doesn’t hold a product catalog, so product feeds come from your catalog — the product feeds guide keeps the ids matching.