REVENUE ATTRIBUTION

Stripe

Connect Stripe with a restricted API key — Attrifast sets up event delivery automatically — and pass the visitor ID into your Checkout Sessions so every payment is attributed to its channel.

Connecting Stripe lets Attrifast turn checkout.session.completed events into attributed orders: each payment is linked to the visitor who made it and the channel that brought them.

Requirements

• The tracker installed and receiving pageviews — attribution works forward from when tracking starts.
• A Pro subscription (Stripe connect is a Pro feature — there's a 7-day free trial).
• You create Stripe Checkout Sessions server-side (Checkout is how payments get linked to visitors — see below).

Step 1 — Connect your Stripe account

What happens when you connect

Attrifast verifies the key, reads your account ID, and creates a webhook endpoint on your Stripe account (subscribed to checkout.session.completed) — you don't configure anything in the Stripe dashboard. You can see the endpoint under Stripe → Developers → Webhooks. Reconnecting replaces it and disconnecting removes it — if you've already rolled the key when you disconnect, the removal can't complete, so delete the endpoint manually in Stripe.

Your key is stored with the connection and is not used to read payment data. To revoke access, disconnect (DELETE /api/stripe/connect/:websiteId) and roll the key in Stripe.

Step 2 — Link payments to visitors

The Attrifast tracker keeps its visitor ID in localStorage under the key _rp_vid. To attribute a payment, pass that ID into the Checkout Session as client_reference_id — that's the only field you need:

On your payment page, read the visitor ID and send it to your server:

const visitorId = localStorage.getItem('_rp_vid');
// include visitorId in your create-checkout request

When creating the Checkout Session server-side:

const session = await stripe.checkout.sessions.create({
  mode: 'payment', // or 'subscription'
  client_reference_id: visitorId, // ← links the payment to the visitor
  line_items: [ /* … */ ],
  success_url: 'https://yoursite.com/thanks',
});

What gets counted

Limitations

• Checkout only — payments that don't go through Stripe Checkout (raw PaymentIntents, invoices) aren't captured yet.
• Subscription renewals aren't captured — renewal charges don't carry the Checkout Session's fields, so today you'll see the first payment of a subscription, not recurring revenue. A subscription that starts with a free trial produces a $0 order at checkout.
• Matching is by visitor ID only. Attrifast deliberately doesn't guess by customer email.
• Not retroactive — payments made before connecting are not imported.
• One Stripe account connects to one Attrifast website (and vice versa).
• No currency conversion — amounts are summed as-is across currencies. If you charge in multiple currencies, revenue totals mix them.

Troubleshooting