Stripe revenue attribution

Connect Stripe to your Clickport site with a read-only restricted key and revenue shows up next to your traffic: a Revenue stat in the dashboard header, a revenue line on the main chart, and payments attributed back to the visit that made them. For sites selling through Stripe Payment Links or hosted Checkout, attribution works with zero code changes.

What you see in the dashboard

Once revenue events exist, a Revenue stat appears in the dashboard header, right next to Engagement (the labels compact to REV and ENG when both are showing). Click it to toggle a revenue line onto the main chart, bucketed exactly like the other metrics. The KPI row itself stays untouched: all standard KPIs keep their place.

Revenue lives in the header next to Engagement; the toggled pill draws the revenue line. The KPI row keeps its standard cells.

Because every attributed payment carries its session's dimensions, revenue works with the rest of the dashboard:

• Cross-filtering: filter to a source, campaign, country, or device and the Revenue stat re-computes for that slice. "How much did the newsletter earn last month" is one click on the Campaigns panel.
• Custom events: Purchases and Refunds appear as events in the Goals panel's custom events list, with revenue totals and averages.
• Goals and funnels: add a custom-event goal on Purchase and funnels can end at the payment, with real amounts behind the conversion step.
• Refunds net out: a refund lands as a negative revenue event attributed to the same session as the original purchase, so per-source revenue stays honest.

How to connect

Setup is one paste. Clickport never asks for your full Stripe secret key, only a restricted key you scope yourself.

1. In Stripe, open Developers → API keys and click Create restricted key.
2. Grant it: Charges — Read, Checkout Sessions — Read. Optionally add Webhook Endpoints — Write (see the sync modes section below). Everything else stays None.
3. Copy the key (it starts with rk_live_).
4. In Clickport, open Settings → Integrations for your site, click Connect with restricted key on the Stripe card, and paste it.

On connect, Clickport validates the key, imports the last 90 days of payments as a backfill, and starts syncing new ones. Revenue from the backfill appears within a few minutes.

Sync modes

• Real-time (recommended): if the key includes Webhook Endpoints — Write, Clickport creates a webhook endpoint on your Stripe account automatically. Payments appear in the dashboard the moment they land. The endpoint is signed and verified; it is removed again when you disconnect.
• Periodic: without the webhook scope, Clickport pulls new payments every 10 minutes. Same data, small delay.

How attribution works

Clickport's tracker knows its own session ID. When a visitor clicks a link to buy.stripe.com or checkout.stripe.com, the tracker appends that session's token to the URL as Stripe's client_reference_id parameter, a passthrough field Stripe returns with the completed payment. Clickport joins it back to the session, and the payment inherits the visit's source, campaign, channel, country, and device.

That covers Stripe Payment Links and hosted Checkout with no code changes at all. Nothing to install beyond the tracker you already have.

Server-created Checkout Sessions

If your backend creates Checkout Sessions via the Stripe API, pass the token yourself. It's one line: read it from the tracker with clickport.checkoutRef() and hand it to Stripe as client_reference_id.

// In the browser: send the token to your backend with the checkout request
const ref = window.clickport.checkoutRef(); // "cp-1234567890"

// On your server: pass it when creating the Checkout Session
const session = await stripe.checkout.sessions.create({
  client_reference_id: ref,
  line_items: [...],
  mode: 'payment',
  success_url: 'https://example.com/thanks',
});

Manual revenue tracking still works

The Stripe integration and the custom events API compose. If you sell through something else entirely, or want revenue on non-payment events, keep using:

clickport.track('Order Completed', { plan: 'yearly' }, { amount: 149, currency: 'EUR' });

The Revenue stat and chart line sum every event that carries revenue, whichever way it got there. Selling through Paddle as well? The Paddle integration runs side by side with this one.

Multi-currency

Amounts are recorded in the currency Stripe charged. Zero-decimal currencies (yen, won, and friends) are handled correctly.

If your store charges in several currencies, pick a reporting currency on the same Integrations tab and Clickport converts every payment into it at the daily European Central Bank reference rate of its payment date: one currency everywhere, past payments included. The original charged amounts are always kept unchanged, and switching back to "As charged" restores them. Without a reporting currency, totals are displayed in whichever currency carries the largest share.

Disconnecting

Click Disconnect Stripe on the Integrations card. Clickport deletes the encrypted key immediately and removes the webhook endpoint it created on your Stripe account. Revenue already imported stays in your analytics; reconnecting later won't double-import it, because every processed payment is remembered by its Stripe ID.

Troubleshooting

"Use a restricted key"

You pasted a full secret key (sk_live_...). Clickport refuses those on purpose — create a restricted key instead (Stripe → Developers → API keys → Create restricted key) and grant only the scopes listed above.

"The key needs read access to Charges"

The restricted key exists but lacks the Charges — Read permission. Edit the key in Stripe, set Charges to Read, and paste it again.

Payments arrive but show as unattributed

• The buyer must have the Clickport tracker loaded on the page where they clicked the checkout link. If your checkout button lives on a page without the tracker (a separate landing page, an email), there's no session to join.
• If the checkout link already carries its own client_reference_id, Clickport never overwrites it — those payments stay unattributed rather than clobbering your reference.
• Server-created Checkout Sessions need the one-line checkoutRef() pass-through shown above.
• Ad blockers that block the tracker also block attribution for that visitor. The payment still counts via Stripe, just without a source.

Revenue totals differ from the Stripe dashboard

Clickport counts succeeded payments minus refunds, timestamped at payment time in your dashboard timezone. Stripe's own reporting may use settlement dates, include fees, or group by UTC days. Small windowing differences at day boundaries are normal.

Privacy and data handling

• Your restricted key (and the webhook signing secret, in real-time mode) is AES-256-GCM-encrypted at rest. Disconnecting deletes it immediately.
• The key is read-only by your own scoping; Clickport cannot modify anything in your Stripe account beyond the webhook endpoint you optionally allow it to create.
• Clickport stores the payment amount, currency, timestamp, and Stripe object IDs. No customer names, emails, or card details are read or stored.
• Attribution uses the session token alone. No cookies, no fingerprinting, no cross-session identity. Connecting or disconnecting the integration is recorded in your site's audit trail.