MetricRaven

Cookieless analytics

Cookieless analytics that still attribute revenue

Before a visitor accepts cookies, MetricRaven stores nothing in their browser and uses a visitor ID that changes daily. You still get traffic, funnels and revenue by channel. With consent, visits connect across days.

  • Nothing stored before consent
  • Raw IP addresses never kept
  • Works with your cookie banner

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 cookieless analytics?

Cookieless analytics counts visits without storing an identifier in the visitor's browser: no cookies, no localStorage. In the EU, the ePrivacy Directive (Article 5(3)) allows storing or reading information on a visitor's device only with their consent, unless it is strictly necessary for the service they asked for. Analytics cookies usually aren't.

Most cookieless tools recognize a visitor for one day at most, using a server-side identifier that rotates daily. That is enough for visitor counts, sources and pages. It is not enough, on its own, to connect a visit on Monday with a payment on Friday.

MetricRaven is cookieless until consent and adds the pieces revenue attribution needs: the visitor ID travels into checkout, signed-in users are linked by your own user ID, and once someone accepts cookies a first-party ID connects their visits for up to a year.

Visitors online now

Public demo · synthetic data · right now

Live demo data

The demo site's realtime view: the page each visitor is on and where they came from. Before consent, the daily visitor ID is enough for this.

Open the demo

Worked example

Which payments get attributed without cookies?

A visitor arrives from a Reddit post on Monday. Here is what happens to their $49 payment in five situations.

Attribution of one payment, with and without consent
SituationConsentCredited to Reddit?Why
Pays on MondayNoYesMonday's daily ID goes into checkout metadata
Signs up Monday, pays FridayNoYesYour user ID links the payment to Monday's visit
Returns anonymously Friday, paysNoNoFriday gets a new daily ID, so Friday's visit gets the credit
Returns anonymously Friday, paysYesYesA first-party ID kept for up to a year connects both visits
Buys on a hosted checkout MondayNoYesThe buyer's email is matched on the thank-you page
  • The gap is the third row: an anonymous visitor who leaves, comes back days later without consent and pays. Every cookieless tool has this gap. Products with sign-up before payment close most of it with identify.
  • Hosted checkouts such as Kajabi, Podia and Ghost use email matching. Without consent, the match covers that day's visit.
  • No payment is lost either way. One that can't be tied to a visit still counts as revenue, shown as Unattributed, so your totals match your payment provider.

What you still get

Revenue reports, without the cookie

From the public demo, running on sample data.

Realtime

Watch visitors arrive on a live globe

Click the Online counter and a full-screen globe opens, with each active visitor at an approximate location next to a live feed of pageviews and goals. The location comes from the IP address, which is never kept.

  • Coordinates rounded to 0.1°
  • Referrers, countries and devices
  • A live feed of visits and goals

Buyer insights

What paying visitors have in common

Which sources and countries buy, how long it takes, and how paying visitors differ from everyone else.

  • Best sources by revenue and purchase rate
  • Days and visits to purchase
  • Revenue share by device, OS and browser

Funnels

From landing page to payment

Funnels can end in a payment from your provider, so drop-off is measured against money, not just clicks.

  • Pages, goals and payments as steps
  • Who left at each step
  • JavaScript errors per step

How it works

Set up without a cookie

Nothing is stored until a visitor agrees, and payments still find their source.

  1. Step 1: Install the script

    Paste one script tag or follow the guide for your platform. To serve it from your own subdomain, add one CNAME record (managed proxy) or use a proxy recipe.

  2. Step 2: Link payments to visits

    Connect your payment provider, pass the day's visitor ID into checkout, and identify signed-in users from the browser or your server. Without consent, the link covers that day's visit.

  3. Step 3: Act on what pays

    See which channels, pages and countries bring paying customers, and fix the funnel steps where they drop off.

Reviews

The numbers you need, nothing more

From people tracking their own sites and revenue with MetricRaven.

★★★★★

Google Analytics always felt like too much. MetricRaven gives me the numbers I actually need, without all the clutter.
Matthew F.

★★★★★

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

★★★★★

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

Privacy

What MetricRaven stores, and when

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 MetricRaven completely cookieless?
Until a visitor consents, yes: no cookies and nothing in localStorage. If your banner calls setConsent(true), MetricRaven keeps a first-party ID in a cookie and localStorage for up to a year, so visits on different days connect. Without that call, it never stores anything.
Do I still need a cookie banner?
That depends on your other scripts, how you use the data and the law where your visitors live. MetricRaven stores nothing in the browser before consent, so it doesn't need a banner to start counting. Ask your own counsel for a definite answer; this page isn't legal advice.
How can cookieless analytics attribute revenue?
Three ways that need no cookie: the day's visitor ID goes into checkout metadata, signed-in users are linked by your user ID, and hosted checkouts are matched by the buyer's email. Payments by anonymous visitors who return on a later day without consent are credited to the later visit.
Where is the data stored?
On servers in the United States (US East). Raw IP addresses are not stored; see the privacy policy and subprocessors.
Does session replay work without consent?
By default, session replay (Growth plan) records only visitors who accepted cookies. Visitors who decline, or haven't chosen yet, are never recorded (consent).

Cookieless analytics with revenue built in

Install one script, connect your payment provider and see which channels bring paying customers, before anyone clicks Accept.

14-day free trial, no card required. See pricing · Read the guide: Consent and visitor IDs