Metrivo
Example using demo data. All names, IDs, timestamps, and amounts on this page are fictional and only illustrate how Metrivo works.
Examples/ChatGPT traffic to revenue

ChatGPT traffic to revenue

This walkthrough follows a single visitor from a ChatGPT answer to a paid Stripe checkout. It is the path Metrivo is designed to track end-to-end when referrer and metadata signals are present.

The scenario

A demo SaaS called Example.saas sells a CSV-cleanup tool. A user asks ChatGPT for help cleaning a messy CSV. ChatGPT's answer cites Example.saas's docs. The user clicks through, signs up, and pays two days later.

Timeline (demo)

2026-03-14 09:12 UTC

ChatGPT referral lands

Visitor opens https://example.saas/docs/csv-cleanup from a ChatGPT answer. Referer: chatgpt.com. Metrivo records source = chatgpt, confidence = high on the session.

2026-03-14 09:14 UTC

Visitor browses

Same session loads /pricing and /docs/quickstart. Both pageviews are stored on session id sess_demo_4a91 with the original chatgpt source.

2026-03-14 09:21 UTC

Signup

Visitor submits the signup form on /signup. Email hash captured: e3b0…demo. Visitor id vid_demo_77ab is now tied to the chatgpt source.

2026-03-16 14:02 UTC

Stripe checkout completes

Stripe Checkout completes with metadata.metrivo_visitor_id = vid_demo_77ab. Webhook arrives at the Metrivo collector.

2026-03-16 14:02 UTC

Payment matched

Metrivo matches the payment to vid_demo_77ab. The $39 payment is attributed to ChatGPT with high confidence.

What the dashboard shows

High confidenceSource: ChatGPTAmount: $39.00Provider: Stripe

The payment is listed under attributed revenue, with the ChatGPT source tag and a link back to the original session and pageviews.

Try this with your own data

Install the tracking script, connect Stripe, and pass metrivo_visitor_id in your checkout metadata.