MetricRaven

Revenue attribution software

Revenue attribution that shows which traffic pays

Revenue attribution links each payment to the visit that brought the customer. MetricRaven does it from your real payments: connect Stripe or another provider, and every channel, campaign, page and country shows the revenue it earned.

  • Works with 10 payment providers
  • Read-only connections
  • 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 is revenue attribution?

Revenue attribution is crediting revenue to the marketing touchpoints that produced it. Instead of counting visits or signups per channel, you count the money each channel brought in.

It needs two records joined together: the visit (where the person came from, which page they landed on, which campaign they clicked) and the payment (how much, when, which plan). Analytics tools have the first. Your payment provider has the second. Revenue attribution is the join.

Once you have the join, the useful number is revenue per visitor. It lets you compare a channel that sends 6,000 visitors with one that sends 1,500 on equal terms.

Revenue by channel

Public demo · synthetic data · last 30 days

Live demo data

Each payment is credited to the channel of the visit that first brought the customer. Compare each row's revenue with its visitors.

Open the demo

Revenue per visitor

Revenue per visitor = attributed revenue ÷ visitors

For a channel that brought $891 from 1,500 visitors: $891 ÷ 1,500 = $0.59 per visitor. See revenue per visitor.

Worked example

Visits say one thing, revenue says another

A SaaS with a $99 plan, over one month. Each customer pays once, so revenue is customers × $99. The numbers are illustrative.

Three channels ranked by visitors, then by revenue per visitor
ChannelVisitorsCustomersRevenueRevenue per visitor
X (Twitter)6,0003$297$0.05
Google search4,00012$1,188$0.30
Reddit1,5009$891$0.59
  • By visitors, X is the best channel. By revenue, it is the worst: 3 × $99 = $297 from 6,000 visitors.
  • Reddit sends a quarter of X's traffic and three times its revenue. Each Reddit visitor is worth $0.59, almost 12 times an X visitor.
  • Without the payment data you would put more time into X. With it, you would put more into Reddit and search. That is the whole point of revenue attribution.

The gap

Why most analytics can't attribute revenue

The visit and the payment live in different systems, and nothing joins them by default.

Analytics plus a payment dashboard

  • Your analytics knows the referrer and UTM tags, but not who paid.
  • Stripe knows who paid, but not the ad, post or search that brought them.
  • Ecommerce events in Google Analytics need a tracking plan, and miss renewals and refunds that happen off your site.
  • You end up comparing channels by visits or signups, which don't pay the bills.

MetricRaven

  • Imports payments, renewals and refunds straight from your provider (connect a payment provider).
  • Passes the visitor ID into checkout, so each payment links to its visit (Stripe Checkout).
  • Credits the payment to the visit that first brought the customer, and keeps later renewals with that channel.
  • Shows revenue next to every channel, referrer, campaign, page, country and device.

What you see

Revenue on every report

Everything here is the public demo running live on its sample data. Open it and click around.

Traffic

Revenue next to every source

Channels, referrers, UTM campaigns, keywords, pages, countries and devices each show revenue, conversion rate and revenue per visitor, not just visits.

  • Rank any breakdown by revenue instead of visitors
  • Filter by any source and see the money follow
  • Export any breakdown to CSV with revenue

Revenue next to every source

Public demo · synthetic data · last 30 days

Live demo data

Funnels

Funnels that end in a payment

Chain pages, goals and payments into an ordered funnel and see where buyers drop off. Paths to payment shows the page sequences people take before they pay.

  • Drop-off and median time between steps
  • Who left at each step
  • JavaScript errors visitors hit at each step

Buyer insights

How buyers differ from everyone else

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

  • Days and visits to purchase
  • Best sources and countries by purchase rate
  • Revenue concentration by device

Payments and subscriptions

Renewals stay with the source that won the customer

New payments and renewals are both credited to the first-touch source, and subscriptions show what keeps paying.

Revenue by first-touch source

Public demo · synthetic data · last 30 days

Live demo data

New payments and renewals per source. A renewal counts for the source of the customer's first visit.

Revenue dashboard docsOpen the demo

Subscriptions and MRR by plan

Public demo · synthetic data · current state

Live demo data

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

Stripe docsOpen the demo

How it works

From one script tag to revenue by source

Most sites have revenue on their channels the same day.

  1. Step 1: Install the script

    Paste one script tag or follow the guide for your platform. A live install check confirms the first pageview as it arrives.

  2. Step 2: Connect payments

    Connect Stripe with the Stripe App or a read-only key, or Lemon Squeezy, Paddle, Polar, Dodo Payments, Creem, Shopify, WooCommerce, RevenueCat, Superwall or Adapty by webhook; anything else can use the Payments API. Pass the visitor ID into checkout or identify signed-in users, and each payment is credited to the visit that first brought the customer.

  3. Step 3: Act on what pays

    Put more into the channels, pages and countries that bring customers, and fix the funnel steps where buyers drop off.

Beyond the website

Revenue attribution for ads, search and apps

The same payment data, joined to the places your traffic starts.

  • Ad spend and ROAS

    Connect Meta Ads or Google Ads, read-only. Daily spend per campaign sits next to the revenue it brought, with ROAS and cost per customer.

  • Keywords with revenue

    Connect Search Console to see the Google queries that bring visitors, with estimated revenue per keyword.

  • MRR and renewals

    Subscriptions, renewals, upgrades and churn from your provider, with MRR over time split into new, expansion, contraction and churn.

  • App purchases

    RevenueCat, Superwall and Adapty purchases, attributed through the same user ID you send from the iOS, Android, React Native or Flutter SDK.

  • AI assistants as a channel

    Visitors from ChatGPT, Perplexity, Claude, Gemini and Copilot get their own AI channel, with the revenue they brought.

  • Affiliates and sponsors

    ref, via and UTM tags group partner traffic, so each affiliate or sponsorship shows its own revenue (campaign links).

Reviews

Where the revenue comes from, in their words

From people tracking their own sites and revenue with MetricRaven.

★★★★★

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

★★★★★

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

★★★★★

I finally know which marketing channels are worth my time and money. That's exactly what I was missing.
Alex T.

Privacy

Revenue attribution 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

What is revenue attribution?
Revenue attribution credits each payment to the marketing touchpoint that brought the customer: a channel, referrer, campaign, keyword or page. It joins analytics data (the visit) with payment data (the money), so you can compare channels by revenue instead of visits.
Which attribution model does MetricRaven use?
First touch: each payment is credited to the visit that first brought the customer, and renewals stay with that channel. Paths to payment shows the full page sequence before a purchase, so you can see what happened between the first visit and the payment. See first-touch vs last-touch attribution.
Which payment providers are supported?
Stripe, Lemon Squeezy, Paddle, Polar, Dodo Payments, Creem, Shopify, WooCommerce, RevenueCat, Superwall and Adapty connect natively. Any other system can send payments and refunds through the Payments API.
Does revenue attribution work without cookies?
Yes, with limits. Before consent, MetricRaven uses a visitor ID that changes daily, so a payment made the same day links to its visit. For purchases days later, identify signed-in users or connect your banner's consent, which keeps a first-party ID for up to a year.
Can I see revenue from visits before I installed MetricRaven?
Payment history can be imported from your provider, but visits from before the script was installed can't be reconstructed. Those payments appear in revenue without a traffic source.

Attribute your revenue automatically

Connect your payment provider and see which channels bring paying customers, from your real payments.

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