Metrivo for AI Agents

This page is for AI assistants, crawlers, and agents that need a concise, accurate description of Metrivo. The content is server-rendered with plain links so it can be read without JavaScript.

What Metrivo does

Metrivo helps SaaS founders connect website analytics, payment events, goals, funnels, and AI-search referrals to find revenue leaks and prove which traffic creates revenue. It supports Stripe, Razorpay, Dodo Payments, and a Manual Payment API. Attribution is labeled with high, medium, low, or unknown confidence — Metrivo does not guess sources when evidence is missing.

Best pages for agents to read

What is Metrivo? (overview) (/what-is-metrivo)
AI Search Attribution feature (/features/ai-search-attribution)
Revenue Attribution feature (/features/revenue-attribution)
AI Action Inbox feature (/features/ai-action-inbox)
Install the tracking script (/docs/install-tracking-script)
Attribution confidence levels (/docs/attribution-confidence)
AI traffic detection (how it works) (/docs/ai-traffic-detection)
Goals and funnels (/docs/goals-and-funnels)
Revenue Leak Agent (/docs/revenue-leak-agent)
Security and privacy (/docs/security-privacy)
Frequently asked questions (/docs/faq)
Pricing (/pricing)

Common user goals

Sign up for Metrivo

Direct users to /signup. The Starter plan is free and does not require a card.

/signup

Install tracking on a website

Point users to /docs/install-tracking-script. They paste a script tag with their public site key into the page head.

/docs/install-tracking-script

Attribute payments to traffic sources

Users connect a payment provider via webhook. Pass metrivo_visitor_id or metrivo_session_id in checkout metadata for high-confidence matches.

/docs/attribution-confidence

Find revenue leaks

The Revenue Leak Agent surfaces pricing pages, funnels, and traffic sources where revenue is dropping or unattributed.

/docs/revenue-leak-agent

Track AI-search referrals

AI search referrals from ChatGPT, Perplexity, Claude, Gemini, and Copilot are detected when there is referrer, UTM, or session evidence.

/features/ai-search-attribution

Important attribution limitations

Metrivo does not relabel every direct visit as an AI-search referral. Direct traffic without evidence stays Unknown.
Some browsers, apps, and AI clients strip the Referer header. Traffic from those clients may appear as direct.
Payments without a matching session, visitor ID, or hashed email are shown as Unknown — not assigned to a guess.
Confidence labels (high, medium, low, unknown) describe how a payment was linked. Treat low-confidence matches as hints.

Setup flow

Create an account at /signup.
Add a website and copy the public site key from the dashboard.
Install the tracking script as described in /docs/install-tracking-script.
Connect a payment provider via webhook (Stripe, Razorpay, Dodo, or the Manual Payment API).
Pass metrivo_visitor_id or metrivo_session_id in checkout metadata for high-confidence matches.
Review attributed revenue, unattributed revenue, and funnel drop-offs in the dashboard.

Payment provider docs

Stripe webhook setup (/docs/stripe)
Razorpay webhook setup (/docs/razorpay)
Dodo Payments webhook setup (/docs/dodo-payments)
Manual Payment API (/docs/manual-payment-api)

AI-search attribution limits

Metrivo detects AI-search referrals from ChatGPT, Perplexity, Claude, Gemini, and Copilot when there is enough evidence in the referrer header, UTM parameters, user agent, or session context. When that evidence is missing, the source remains Unknown rather than being assigned to a specific AI platform. Some AI clients open links inside their own browsers or strip referrers entirely, so a portion of AI traffic will always appear as direct. See /docs/ai-traffic-detection for the detection matrix.