Stripe Revenue Attribution

Connect your Stripe account to attribute revenue to visitor sessions. See which pages, referrers, UTM campaigns, and devices are driving your sales.

How to connect Stripe

Here's an exact step-by-step tutorial on how to integrate Stripe.

1. Head to API keys in Stripe
2. Create a restricted API key
3. Select "Providing this key for another website"
4. Name the key whatever you like ("Visitors")
5. Add "https://visitors.now" as the URL.
6. Hit "Create restricted key"
7. Copy the generated API key ("rk_live_...")
8. Head to your project's Settings
9. Navigate to Integrations
10. Hit the connect button for Stripe
11. Paste it in your API key
12. Hit "Connect"

We'll then automatically create a webhook endpoint for your Stripe account and Visitors will begin receiving transaction events from Stripe.

Enable persist mode

Without this we can't attribute transactions to real visitors. This will enable cookie-based tracking allowing you to read the visitor cookie.

1<script
2  src="https://cdn.visitors.now/v.js"
3  data-token="YOUR_TOKEN"
4  data-persist>
5</script>

How attribution works

When a Stripe event comes in we resolve the visitor through a fallback chain:

1. Checkout metadata
2. Any previous attribution
3. Email matching

Checkout metadata is the most reliable, if not we will then check for any previous purchase or subscription event that matches which might already have attribution, otherwise we will make a last ditch attempt to find a profile associated with that payments email.

Stripe Checkout integration

When creating a Stripe Checkout session on your server, read the visitor cookie from the incoming request and pass it as metadata to your Stripe checkout.

1import { cookies } from "next/headers";
2import Stripe from "stripe";
3
4const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);
5
6export async function POST(request: Request) {
7  const visitor = (await cookies()).get("visitor")?.value;
8
9  const session = await stripe.checkout.sessions.create({
10    line_items: [{ price: "price_xxx", quantity: 1 }],
11    mode: "payment", // or "subscription"
12    success_url: "https://example.com/success",
13    metadata: { visitor },
14  });
15
16  return Response.json({ url: session.url });
17}

Email fallback with identify

If you can't pass the visitor cookie in every checkout (e.g. the purchase happens on a different domain), Visitors can still attribute revenue by matching the Stripe customer's email to an identified visitor.

Call visitors.identify() with the user's email when they sign in:

1visitors.identify({
2  id: "user_123",
3  name: "Jane Smith",
4  email: "jane@example.com",
5  // ...
6})

When a Stripe event comes in without visitor metadata, Visitors will look up the customer email and match it to the identified profile. This is less reliable than passing metadata directly, but acts as a useful fallback.

Learn more about identifying users.

Troubleshooting

If revenue is showing up but it's not being attributed, ensure that:

1. You are in persist mode
2. You are reading the visitor cookie set by persist mode correctly
3. You are passing it in metadata when creating the checkout session.

If you are doing all that and it's still not attributing correctly, contact our support team and we'll help you to diagnose the root cause.