MetricRaven

Stripe revenue analytics

Stripe analytics that show where revenue comes from

Stripe tells you who paid. MetricRaven tells you what brought them: the channel, referrer, UTM campaign, keyword and page behind every Stripe payment, next to MRR, churn and lifetime value.

  • One-click Stripe App
  • Read-only access
  • 14-day free trial, no card

Orbit Analytics

orbit.metricraven.com · Last 30 days

Traffic overview

Visitors
1.6k
11.8%
Revenue
$20.9K
14.5%
Conversion rate
19.2%
3.2%
Rev/visitor
$13.21
2.4%
Bounce rate
33.6%
1.7%
Session time
2m 55s
2.8%
Online
7

% vs previous period · USD · UTC · dashed = partial period · grey dashed = previous period

The public live demo with sample data.

What Stripe knows, and what it doesn't

Stripe records every charge, subscription, invoice and refund. What it has no record of is the visit that led to the payment: the ad, the Reddit thread, the Google search or the newsletter link.

Stripe's way to attach your own data to a payment is metadata: key-value pairs on objects such as Checkout Sessions, PaymentIntents and subscriptions. Stripe analytics that answer "which traffic pays?" need something to put the visit into that metadata, and something to read it back next to your traffic.

MetricRaven does both. Its script records the visit, your checkout passes the visitor ID into Stripe metadata, and MetricRaven reads the payment back through a read-only connection.

Revenue by first-touch source

Public demo · synthetic data · last 30 days

Live demo data

Payments and renewals, each credited to the source of the customer's first visit.

Open the demo

What you add to Checkout

For subscriptions, use subscription_data instead of payment_intent_data, so renewals carry it too. Full examples: Stripe Checkout.

checkout.js
// Server-side. visitorId came from the browser.
const session = await stripe.checkout.sessions.create({
  // …mode, line_items, success_url
  metadata: { metricraven_visitor_id: visitorId },
  payment_intent_data: {
    metadata: { metricraven_visitor_id: visitorId },
  },
});

Stripe UTM tracking

UTM parameters sit on the URL a visitor lands on. By the time they reach checkout, they have usually clicked through several pages, and the tags are gone from the address bar.

You don't need to copy each tag into Stripe. MetricRaven stores the UTM source, medium, campaign, term and content on the visit, so one visitor ID in metadata is enough: the payment inherits every tag, the referrer and the landing page of the visit that first brought the customer.

Payment Links can't carry a different visitor ID per buyer. For those, add a small webhook or match by the buyer's email (Payment Links).

Revenue by UTM campaign

Public demo · synthetic data · last 30 days

Live demo data

Each utm_campaign with its visitors and the revenue its visitors paid.

Open the demo

Subscriptions

MRR and plans, next to where customers came from

Subscription state comes from your provider, and every payment keeps the channel that brought the customer.

Subscriptions and MRR by plan

Public demo · synthetic data · current state

Live demo data

Active, trialing, at-risk and canceled subscriptions per plan, with estimated MRR.

Stripe docsOpen the demo

Purchase rate by channel

Public demo · synthetic data · last 30 days

Live demo data

The share of each channel's visitors who paid, how long they took and the revenue.

Buyer insights docsOpen the demo

In the dashboard

Follow a Stripe payment back to its first visit

From the public demo, running on sample data.

Buyer insights

When and how customers buy

How many days and visits it takes to buy, which sources buy fastest and what paying visitors did first.

  • Days and visits to purchase
  • Top sources by purchase rate
  • Revenue concentration by device and browser

Funnels

From pricing page to paid

Build a funnel that ends in a Stripe payment, or in a lifecycle goal such as a converted trial, and see who left at each step.

  • Pages, goals and payments as steps
  • Median time between steps
  • The people behind each drop-off

How it works

Connect Stripe in three steps

Revenue imports first; attribution starts with the next checkout.

  1. Step 1: Add the script

    Paste one script tag or follow the guide for your platform, so every visit has an ID to hand to checkout.

  2. Step 2: Install the Stripe App

    MetricRaven is on the Stripe App Marketplace and asks only for read permissions; a restricted key works too. Past payments, subscriptions and refunds import, and new ones arrive as they happen.

  3. Step 3: Pass the visitor ID

    Add it to Checkout or PaymentIntent metadata and identify signed-in users. Payments, renewals and refunds then show under the source that won the customer.

Stripe revenue analytics

Everything from Stripe, joined to your traffic

The Revenue tab answers how the business is doing. The Traffic tab answers where the money comes from.

  • Revenue by source

    Every channel, referrer, campaign, keyword, page, country and device shows revenue, customers and revenue per visitor.

  • MRR movements

    MRR by day, week or month, split into new, expansion, contraction and churn, reconstructed for up to two years before you connected.

  • Subscriptions and churn

    Active, trialing, at-risk and canceled subscriptions by plan, plus trial, upgrade, cancellation and churn events as goals for funnels and alerts.

  • Lifetime value by plan

    Average and median lifetime value per customer, by plan, over every payment they made.

  • Refunds and disputes

    Refunds and lost disputes are deducted from revenue, dated when they happen. Revenue is captured amounts before Stripe fees.

  • Any currency

    Payments in other currencies convert to your reporting currency at the European Central Bank rate of each payment's day.

Reviews

Seeing where the money comes from

From people tracking their own sites and revenue with MetricRaven.

★★★★★

I barely use PostHog anymore. MetricRaven makes it so much easier to see where my revenue is coming from.
Victor H.

★★★★★

Turns out my biggest traffic sources weren't bringing in the most money. MetricRaven made that obvious.
Daniel R.

★★★★★

Set it up in minutes and had everything I needed in one place. So much easier than I expected.
Sophie M.

Privacy

Useful analytics without following people around

MetricRaven works before anyone accepts cookies and connects visits across days once storage is allowed. You decide how your banner and MetricRaven fit together.

  • No persistent ID before consent

    Until a visitor agrees, visits use a server-derived ID that changes daily. Nothing that identifies them is stored in the browser.

  • Raw IP addresses are never kept

    An IP is only used to look up an approximate location. Coordinates are rounded to 0.1°, and unknown locations are left out.

  • Works with your cookie banner

    Call setConsent from your banner and MetricRaven keeps a first-party ID for up to a year, so return visits connect.

  • Erase a person on request

    Delete one person's events and identity records from the dashboard or the API, for example after a deletion request.

MCP server and CLI

MetricRaven for AI agents

Connect MetricRaven to Cursor, Claude Code, Codex or ChatGPT with MCP, or use the CLI from any terminal. Ask in plain English to analyze traffic, understand revenue and manage your account.

FAQ

Questions

Is the MetricRaven Stripe App read-only?
Yes. It asks for read access to charges, refunds, customers, events, Checkout Sessions, PaymentIntents, subscriptions, invoices, disputes, products and prices. MetricRaven never creates charges or issues refunds (permissions).
How do I track UTM parameters in Stripe?
Let MetricRaven record the UTM tags on the visit and pass only the visitor ID in Checkout metadata. The payment then inherits the campaign, source, medium, referrer and landing page of the visit that first brought the customer, without copying tags into Stripe.
Do Stripe Payment Links work?
Payment Link revenue imports like any other payment. Linking it to a visit needs a small webhook that copies the visitor ID into metadata, or an email match on the page the link redirects to (Payment Links).
Does it work with Kajabi, Podia or Ghost on Stripe?
Yes, when those platforms charge through your own Stripe account. Their checkouts can't carry the visitor ID, so you send the buyer's email from the thank-you page and MetricRaven matches the payment (Kajabi, Podia, Ghost).
Is revenue shown before or after Stripe fees?
Before. Revenue is the captured amount, with refunds and lost disputes deducted. To estimate what Stripe keeps, use the Stripe fee calculator.

Connect Stripe and see what pays

Install the Stripe App and see revenue by channel, campaign and page from your real Stripe payments.

14-day free trial, no card required. See pricing · Read the guide: Connect Stripe