Stripe revenue by traffic source

Last updated 28 October 2026. Setup details come from the Stripe setup guide and revenue docs. Need the step-by-step technical guide? Go to /integrations/stripe.

In short#

• Connect: create a Stripe restricted key with five permissions and paste it in Settings → Revenue. traffic.cx creates the webhook and imports the last 90 days of payments.
• Link: pass the visitor's pageview ID (tcx_pvid) into Checkout Session metadata, and into the subscription's metadata so renewals carry it. For Payment Links, pass it as client_reference_id.
• Read: revenue, paying customers, conversion rate and revenue per visitor by channel, source, campaign, landing page, country and device.
• Cost: included on every plan, Free too: one site, 3,000 events a month, no card.

What Stripe payments look like in traffic.cx#

traffic.cx reads Checkout Sessions, Payment Links, PaymentIntents, subscription invoices and refunds. Each payment is matched to a recorded visit, and the Revenue page shows, for each channel, source, campaign and landing page:

Payments in other currencies are converted to your site's reporting currency using historical European Central Bank reference rates. With Stripe, traffic.cx counts the amount Stripe reports; it doesn't remove sales tax the way merchant-of-record providers do (definitions).

How a Stripe payment finds its visit#

1. The visit. The traffic.cx tracker records the visit with its source, campaign and landing page.
2. The checkout. When the visitor starts checkout, your page reads trafficcx.pageviewId() (and, in cookie mode, trafficcx.visitorId()) and your server adds them to the Checkout Session's metadata.
3. The payment. Stripe sends the payment to traffic.cx. traffic.cx finds the pageview, then credits the right visit using your attribution model: last non-direct (default) or first touch, within a lookback of 90 days by default (7 to 365 days).
4. Renewals. A renewal for a known customer inherits the attribution of that customer's first payment, so a subscriber who came from a newsletter keeps crediting the newsletter.
5. Refunds. A refund is subtracted on the day it happens and credited to the payment it refunds.
6. No link. A payment with no matching visit or earlier customer payment stays in the totals as Unattributed.

In the default cookieless mode, the pageview ID links a payment to the visit where checkout started; daily-rotating visitor IDs don't connect visits across days. Longer journeys need the optional cookie mode (same browser only) or an earlier payment from the same customer (cookieless vs cookie mode).

Connect Stripe in three steps#

Install and verify the tracker first. You need an owner or admin role in traffic.cx and access to create a Stripe restricted key. Use a separate traffic.cx test site with a Stripe test-mode key while you set up.

1. Create a restricted key and connect#

In Stripe, open Developers → API keys → Create restricted key, with these permissions and nothing else:

In traffic.cx, open Settings → Revenue, choose Connect next to Stripe and paste the key. traffic.cx checks each permission, creates a webhook endpoint in your Stripe account, stores its signing secret encrypted, and imports the last 90 days of payments. Imported payments without visit IDs count as Unattributed.

2. Pass the visitor's IDs into checkout#

Put tcx_pvid (and tcx_vid in cookie mode) in the Checkout Session's metadata. For subscriptions, also put them in subscription_data.metadata, so renewals carry them. For one-off payments, session metadata is enough; with your own PaymentIntents, put the keys in the PaymentIntent's metadata. The Stripe guide has the server code, and the revenue docs show how to read the IDs in the browser and validate them on your server.

Payment Links: when the visitor clicks the link, add the pageview ID as client_reference_id with a tcx_ prefix. Don't use this if client_reference_id already carries another reference your app needs.

3. Test one payment#

Open a tagged page on your site (for example with ?utm_source=setup-check&utm_medium=email&utm_campaign=integration-test), start checkout from that visit, and complete a Stripe test-mode payment. In Settings → Revenue, check the webhook log, then find the payment on the Revenue page with the right source and campaign. For a subscription, check the first invoice, a renewal and a refund too.

The Stripe details traffic.cx handles#

• Counted once. Each payment is recorded once, however many of these events describe it.
• Missed webhooks. Failed deliveries are retried with growing pauses, and an hourly sync reads the last two days again.
• Pinned API version. The webhook endpoint is pinned to Stripe API version 2024-06-20; don't change it independently of the connector.
• Disconnecting removes the webhook endpoint; payments already recorded stay.

When a payment shows as Unattributed#

• A Stripe connection alone doesn't supply browser IDs. Check the actual session or PaymentIntent metadata for tcx_pvid.
• The tracker was blocked, or checkout ran before it loaded, so there was no pageview ID.
• The buyer returned on a later day or another device in cookieless mode.
• It's an imported payment from before you installed traffic.cx.

The UTM campaign guide walks through fixing Unattributed revenue.

Pricing#

Sign up with Google or email and start on the Free plan: every feature on one site, no card and no trial clock. Revenue attribution is included on every plan, Free too. Paid plans add more events, more sites, your full history, the API and teams. A payment received through a provider integration doesn't count as an event. See pricing.

See which traffic pays you#

Start free · Stripe setup guide · How revenue attribution works · Pricing

Using another provider? See Lemon Squeezy, Polar, Dodo Payments or the Payments API.