Revenue

Revenue arrives from your billing provider's own webhooks, is verified with that provider's proof, normalised to one event model, converted to your project currency, and linked to the person who paid. It then works everywhere events do: as a funnel step, an experiment metric, or a breakdown.

How it fits togetherCopy Anchor Link

1. Create an integration for a provider. You get a webhook URL on your region's ingest host: https://eu.i.analytics.atrix.dev/wh/{provider}/{token}.
2. Paste the URL into the provider, and give Atrix the provider's signing secret where it has one.
3. Link customers to people from your app with setRevenueCustomer, so revenue lands on the right person.

The token in the URL only routes the delivery. Authenticity always comes from the provider's own proof, never from the URL.

Create an integrationCopy Anchor Link

In the console: Settings → Integrations → Connect, which shows the webhook URL, lets you rotate it, and holds the Google Play price catalogue. The same through the API:

curl -X POST "https://app.analytics.atrix.dev/v1/projects/$PROJECT_ID/integrations" \
  -H "Authorization: Bearer $ATRIX_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: stripe-setup-1' \
  -d '{ "provider": "stripe", "name": "Stripe live", "secret": "whsec_…" }'

The response includes webhook_url. Secrets are sealed with AES-256-GCM and never returned (only secret_last4). Reads need projects:read; changes need projects:write. PATCH updates name, config, secret (rotation) or status (active / paused); POST …/rotate-token issues a new URL; DELETE disconnects. A paused integration acknowledges deliveries without ingesting them.

Per providerCopy Anchor Link

Link customers to peopleCopy Anchor Link

import * as atrix from "@atrix.dev/analytics-web";

// After checkout, with the provider's customer id:
atrix.setRevenueCustomer("cus_Nffrfeu", { provider: "stripe" });

This sends a $revenue_customer event for the current user. Every SDK has it (setRevenueCustomer in JavaScript, set_revenue_customer in Python, SetRevenueCustomer in Go). Links are picked up within about 30 seconds, and revenue that arrived before the link is attributed retroactively.

What you getCopy Anchor Link

• Event types: initial_purchase, renewal, trial_started, trial_converted, cancellation, refund, billing_issue, product_change, one_time_purchase. Redelivered webhooks never double count.
• Currency: amounts are converted into your project currency and USD with the European Central Bank's daily reference rate for the event date, in integer minor units. Currencies the ECB does not publish (for example PKR and AED) are kept in their original currency with the rate recorded as unknown.
• A $revenue event on the paying person, with $revenue_minor, $currency, $revenue_event_type, $revenue_provider, $product_id and $subscription_id, so revenue works in funnels, trends and experiments.
• Revenue insights through the query API: mrr, arr, mrr_movements (new, reactivation, expansion, contraction, churned), revenue (gross, refunds, net), arpu, arppu, ltv by signup cohort, and refund_rate, with breakdowns by product, country, platform, store or provider.
• SQL: the revenue_events table; see SQL.