Find the leak costing you revenue today.
Connect traffic, funnels, AI-search referrals, and payments. Metrivo shows the source, page, funnel step, or checkout path losing revenue, with the evidence behind the fix.
Start with one website and one payment path. Seven days free, no credit card, and no fake certainty.
- Traffic
- Attribution
- Checkout
- Payment
- Revenue Leak
7 days free. No credit card. Setup takes a few minutes.
Built for SaaS founders, indie hackers, and operators.
See revenue by source
Payments are tied back when session, visitor, customer, email-hash, metadata, or provider evidence supports it — unknown stays visible.
Spot where the path breaks
See where visitors stall across pricing, signup, checkout, or payment paths, ranked by revenue impact.
Ship the next step, measure lift
Turn evidence into fix drafts or experiments, then see the revenue difference.
- No credit card required
- Privacy-friendly, cookieless tracking
- Stripe, Dodo, Razorpay, Paddle & Lemon Squeezy
- Live in a few minutes
Watch the leak workflow
A 20-second walkthrough of the Metrivo revenue workflow.
Supported payment sources
Supported payment integrations for source-to-revenue attribution.
- StripeStripe supported payment integration
- RazorpayRazorpay supported payment integration
- Dodo PaymentsDodo Payments supported payment integration
- PaddlePaddle supported payment integration
- Lemon SqueezyLemon Squeezy supported payment integration
- Manual Payment APIManual Payment API supported payment integration
Your analytics tools show activity. They do not tell you which leak to fix first.
Metrivo is for founders who already have traffic and payments, but still cannot see where revenue is slipping away.
Traffic reports stop too early
Visits, events, and UTMs do not explain which source becomes paid revenue.
Funnel leaks hide across tools
Pricing, signup, checkout, and payment evidence usually live in different tabs.
AI-search influence gets blurred
Detected AI referrals, UTMs, landing URLs, and payment metadata need confidence labels, not guesses.
What you get after one clean setup.
One website, one payment path, and one ranked revenue leak with the evidence that supports it.
See revenue by source
Payments are tied back when session, visitor, customer, email-hash, metadata, or provider evidence supports it — unknown stays visible.
Spot where the path breaks
See where visitors stall across pricing, signup, checkout, or payment paths, ranked by revenue impact.
Ship the next step, measure lift
Turn evidence into fix drafts or experiments, then see the revenue difference.
Proof you can inspect before signing up.
No fake quotes, no inflated logos, and no made-up user counts. The proof is the product sample, docs, and constraints.
- Seeded demo, clearly labeledUse /demo to inspect the product sample without signup or live customer claims.
- Privacy limits in writingNo session replay, DOM recording, keystroke tracking, or raw input-value capture.
- Payment proof requiredIntegrations become active only after signed webhook delivery or authenticated Manual API evidence.
Use the setup path that fits your site.
WordPress and the read-only CLI are already included in this repo. Shopify is a setup guide today, not a published Shopify plugin or App Store app.
Three steps to your first revenue-leak evidence.
Start with one website and one payment path. If the data is not ready, Metrivo shows what is missing before it calls anything a leak.
See how Metrivo finds the leak.
Pick an industry for a seeded preview, then open the seeded interactive demo to explore attribution, the geo leak map, before/after metrics, and fixes.
Revenue leak preview
GlowKart Beauty
glowkart.example - $120k-$180k/month
Estimated monthly leak
$31.2k/month
Attribution confidence
High
Affected metric
Cart-to-payment -25%
Potential recovery
27%
Estimate only.
Revenue leak found
Creator traffic adds to cart, then shipping costs stall checkout.
Leak source / channel
Creator and paid social campaigns
What changes when revenue is the source of truth.
Google Analytics and PostHog can answer many traffic and product questions. Metrivo is built around source-to-revenue evidence, missing data, and the next founder-friendly action.
| Capability | Google Analytics | PostHog | Metrivo |
|---|---|---|---|
| Traffic analytics | Yes | Yes | Yes |
| Product behavior | Limited | Built-in | Built-in |
| Source-to-revenue attribution | Manual setup | Manual setup | Built-in |
| UTM missing detection | Limited | Manual setup | Built-in |
| Revenue leak detection | Manual setup | Manual setup | Built-in |
| Suggested fixes | Limited | Limited | Built-in |
| Before/after experiment tracking | Manual setup | Built-in | Built-in |
| Founder-friendly next action | Manual setup | Manual setup | Built-in |
Revenue attribution, leak detection, and AI-search analytics in one place.
One workflow instead of ten tabs. Every capability below ties back to making, recovering, or protecting revenue.
Revenue Leak Agent
Find leaking sources, pages, funnels, checkout paths, setup gaps, unattributed revenue, and AI-search traffic when connected data supports the finding.
Learn moreAI Action Inbox
Prioritize actions with evidence, confidence, severity, estimated impact, and a next step, so the founder sees what to do first.
Learn moreFix Generator
Draft CTA variants, FAQ blocks, landing sections, pricing copy, AI-search landing pages, and checkout recovery emails for review and testing.
Learn moreBehavior Revenue Maps
Privacy-friendly click heatmaps, rage clicks, dead clicks, and scroll depth — segmented by who converted — so you see where pages frustrate buyers before checkout. The Leak Agent reads these signals to explain why a step leaks.
Learn moreRevenue Memory
Record leaks found, fixes generated, experiments launched, results measured, wins, losses, and approaches to avoid repeating.
Learn moreAttribution Ledger
Keep auditable payment attribution decisions with source, confidence, method, and evidence. Ledger writes are append-only and do not block ingestion.
Learn moreAI Search Revenue Attribution
Track detectable ChatGPT, Perplexity, Gemini, Claude, Copilot, and AI Overview-related traffic only where referrer, UTM, landing URL, or payment evidence exists.
Learn moreSubscription Metrics
Measure MRR, ARR, ARPU, active subscribers, churn, net-new MRR, cohorts, failed payments, and at-risk payments from your payment events.
Learn moreMulti-provider Payment Attribution
Use Stripe, Dodo, Razorpay, Paddle, and Lemon Squeezy webhooks, or send custom events through the scoped Manual Payment API. Hosted checkout metadata still has to be passed by your checkout code.
Learn more
Conservative attribution beats confident guesses.
Metrivo labels uncertainty, keeps missing data visible, and uses a narrow payment connection model.
Confidence labels
Attribution uses high, medium, low, and unknown labels so you can separate direct evidence from inferred or missing evidence.
Privacy-friendly tracking
The tracker respects browser Do Not Track, supports opt-out rules, and does not use session replay, DOM recording, keystroke tracking, or input-value capture.
Hashed sensitive fields
Tracking ingestion stores IP hashes instead of raw IP addresses, customer emails are normalized to hashes, and API keys are hashed before storage.
Workspace isolation
Supabase Row Level Security and server-side workspace checks protect tenant data. The Manual Payment API resolves workspace ownership from the API key, not client input.
Webhook proof before connected
Payment integrations are not treated as active until signed delivery or authenticated payment evidence is received.
Narrow payment access
Supported payment integrations use signed inbound webhooks. Metrivo listens for events instead of asking for money-moving provider API keys.
Simple pricing for finding the next provable leak.
Simple plans, free to start. Founding users get 50% off the yearly plan for sending feedback.
Questions, answered.
What is Metrivo?
Metrivo is a revenue intelligence platform for SaaS founders. It connects traffic, attribution, checkout, payments, and AI-search referrals into one revenue path, so you can see which traffic source makes you revenue, find where revenue leaks out, and decide what to fix next — with evidence and a draft fix, not just a dashboard.
What is a revenue leak in SaaS?
A revenue leak is any point where potential revenue is lost: a traffic source that never converts, a pricing page that loses buyers, a funnel step with unusual drop-off, a failing checkout, or AI-search visitors who buy but are never attributed. Metrivo finds these leaks by connecting traffic and payment evidence, then ranks them by estimated impact.
How is Metrivo different from Google Analytics or Plausible?
Google Analytics and Plausible show what happened: visits, sources, and events. Metrivo connects those events to actual payments, labels each attribution with a confidence level, then recommends the next fix, drafts it, and measures the result as an experiment. It is a revenue workflow, not a traffic report.
How does Metrivo track ChatGPT, Perplexity, and other AI search traffic?
Metrivo detects AI-search referrals from ChatGPT, Perplexity, Gemini, Claude, Copilot, and AI Overviews using referrer, UTM, landing URL, or payment metadata evidence — and ties them to revenue. It only labels AI traffic when evidence exists; unknown direct traffic stays unknown instead of being inflated.
Does Metrivo track MRR and churn?
Yes. Metrivo computes MRR, ARR, ARPU, active subscribers, net-new MRR, churn, failed payments, and cohort retention from payment-derived subscription events.
Which payment providers does Metrivo support?
Metrivo includes webhook support for Stripe, Dodo Payments, Razorpay, Paddle, and Lemon Squeezy. Custom payment paths can send events through the Manual Payment API with a server-side payments:write key.
Does Metrivo change my website automatically?
No. The Fix Generator creates drafts for founder review, and experiments are created from approved fixes. Metrivo does not promise instant website changes or automatic revenue recovery.
Is attribution perfect?
No attribution is. Metrivo shows confidence labels and keeps unattributed revenue visible instead of hiding it. A payment is only matched when session, visitor, customer, email hash, or metadata evidence supports the match.
Is it safe to connect payment data?
Yes. Supported payment providers use signed inbound webhooks, webhook secrets are encrypted before storage, and the Manual Payment API is scoped by server-side payments:write keys. Metrivo listens for events instead of asking for money-moving provider API keys.
Who is Metrivo best for?
Metrivo is best for SaaS founders, indie hackers, and operators with live traffic and payments. If you are pre-launch, you can install tracking and goals now so attribution works from day one — leak detection becomes useful once real traffic and payment data flow.
What is the Metrivo Founding User Program?
Try Metrivo on the 7-day free trial with one website and one payment path. Send your feedback to support@metrivo.co and get 50% off the yearly plan as a thank-you.
Ready to see where your revenue leaks out?
Install one script, connect one payment path, and let the Revenue Leak Agent rank what to fix first — with the evidence behind it.
7 days free. No credit card.
Compare Metrivo
