Revenue tracking

Send the amount with the event and it follows the user everywhere: which referrer paid for itself, which page sold, what a session was worth.

Attribution

Revenue by source, page and campaign

Revenue is attributed to the session it happened in. So every table on the overview that ranks sessions can rank money instead: referrers, UTM campaigns, entry pages, countries.

Referrers and campaigns by revenue
A Revenue column with its share of the total, next to sessions.
Entry pages that sell
The page people landed on before they paid, not just the page they paid on.
On every overview chart
Pick Revenue as the metric, or see it as green bars behind visitors.
Profiles and sessions

Down to the person

Each payment lands on a profile and on a session. The profile page sums it up, the session list shows what each visit was worth, and the events list shows the amount on the row.

Lifetime revenue per profile
A Revenue tile next to events, sessions and conversions.
Revenue per session
The visit that paid, in the sessions table and on the session page.
Filter and group by it
revenue is a filter property, and "Sum of revenue" is a metric in any report.
Server-side by default

Only from where you trust

A payment is a fact your server knows. Revenue is accepted with the client secret, from your backend or your payment webhook. Browsers can send it only if you switch that on for the project.

Integers, in cents
op.revenue(2900) is $29.00. No floats, no strings, no rounding surprises.
Secret required unless you opt out
"Allow unsafe revenue tracking" is off until you turn it on.
Checkout flows in the browser
pendingRevenue before the redirect, flushRevenue on the thank-you page.

Where the money shows up

  • A metric in any report"Sum of revenue" per day, by plan, by country, by campaign.
  • In the sessions tableA Revenue column, so the visits that paid are one sort away.
  • On the project cardVisitors, sessions and revenue for every project, before you open one.
  • On the event rowRevenue events show their amount in the events list.
  • A message when someone paysA notification rule on the revenue event, to Slack, Discord or a webhook.
  • Exported with everything elseRevenue is a column on the event, so it is in every S3 or GCS export.
How it works

How revenue gets in

No payment integration to set up. Send one event per charge from the webhook you already have.

  1. 1

    Send the amount

    From your backend with the client secret, or from the browser once you allow it.

    // in your payment webhook
    await op.revenue(2900, {
    plan: 'pro',
    profileId: customer.id,
    });
  2. 2

    Or stage it through checkout

    The web SDK keeps a pending amount until the thank-you page.

    // in the browser, before checkout
    op.pendingRevenue(2900);
    // on the thank-you page
    op.flushRevenue();
  3. 3

    Read it everywhere

    Overview, sessions, profiles, reports and exports. One currency, shown as USD.

Works together with

Frequently asked questions

Common questions about tracking revenue with OpenPanel.

Start understanding your users today

One script on your site, or one SDK call in your app, and the first events show up within a minute. 30-day free trial, no credit card.

Cloud from $2.50 a month, or self-host for free.