Revenue & Stripe

Connect Stripe and OakData turns your subscription data into revenue analytics — MRR, ARR, churn and ARPU on a dedicated Revenue dashboard — and links each paying customer back to the person who visited your site, so you can see who upgraded, to which plan, and their lifetime value, right on their profile in People.

The connection uses a read-only restricted API key. OakData can only read your customers, subscriptions and charges — it can never create charges, issue refunds, or change anything in your Stripe account. There are no webhooks for you to configure: OakData backfills on connect and refreshes whenever you open the Revenue dashboard.

1. Create a read-only key

Open Stripe's Create restricted key form — the name (OakData) and the read-only permissions are already filled in, so you just click Create key. It grants Read access to:

Copy the key — it starts with rk_live_ (or rk_test_ in test mode).

2. Paste it into OakData

Go to Project → Settings → Stripe revenue, paste the rk_… key, and click Connect Stripe. OakData validates the key, pulls in your customers, subscriptions and charges, and computes MRR. Open the Revenue tab to see it.

3. Attribute revenue to the right person

To link a Stripe customer to a tracked visitor, OakData resolves in this order:

The visitor id lives in the oak_did cookie (set by the tracking SDK) and is also available client-side as oak.getDistinctId(). Read it when you create the checkout and attach it as metadata:

import { cookies } from 'next/headers'
import Stripe from 'stripe'

const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!)

export async function POST(req: Request) {
  const oakId = (await cookies()).get('oak_did')?.value

  const session = await stripe.checkout.sessions.create({
    mode: 'subscription',
    line_items: [{ price: 'price_123', quantity: 1 }],
    success_url: 'https://example.com/thanks',
    // Copy the id onto the subscription (and customer) so OakData's
    // sync sees it on the persisted objects, not just the session.
    metadata: { oak_distinct_id: oakId ?? '' },
    subscription_data: { metadata: { oak_distinct_id: oakId ?? '' } },
  })

  return Response.json({ url: session.url })
}

Email fallback

Even without metadata, identified people are matched by email. Make sure you call oak.identify() with an emailtrait so there's something to match on:

oak.identify('user_123', { email: 'sam@example.com', name: 'Sam Rivera' })

What you get

FAQ