Connect Stripe

Two parts: import payments with a restricted key, then link checkouts to visits. You can import revenue before adding attribution.

Import payments

1. Open Settings → Integrations → Stripe

   In your MetricRaven site settings.

2. Create a live restricted key in Stripe

   In your Stripe API keys, create a live restricted key. If Stripe asks how you will use it, choose “Providing this key to a third-party application”, enter MetricRaven and https://metricraven.com, then select “Customize permissions for this key”.

   Set every permission group to None, then grant Read only for the resources in the permissions table.

3. Paste the key and choose Connect Stripe

   Paste the rk_live_… key. Publishable keys and unrestricted secret keys are not accepted.

4. Wait for Connected

   The status changes from Importing history to Connected. Large histories import in batches; Last sync and the scanned-payment count show progress.

Required read permissions

Attribute checkout to a visit

1. Read the visitor ID in the browser

   Pass it to your existing checkout endpoint:

   script.js

   Copy

   1

   2

   3

   4

   // Read this in the visitor's browser when they start checkout.
   const visitorId = window.analytics?.getVisitorId() ?? null;
   // Send visitorId to your own checkout endpoint alongside its usual request data.
   // Use the authenticated user ID from your backend; do not trust a browser-supplied user ID.

2. Add metadata when creating the Checkout Session

   Replace the example price, URLs and user ID with your own. For a guest checkout, omit the user ID if you don't have one.

   One-time Stripe Checkout

   Copy

   1

   2

   3

   4

   5

   6

   7

   8

   9

   10

   11

   12

   13

   14

   15

   // In your existing server-side checkout handler.
   // stripe is your initialized Stripe client; visitorId came from your browser.
   const attribution = {
     metricraven_visitor_id: visitorId || "",
     metricraven_user_id: authenticatedUser.id,
     metricraven_plan: "pro",
   };
   const session = await stripe.checkout.sessions.create({
     mode: "payment",
     line_items: [{ price: "YOUR_STRIPE_PRICE_ID", quantity: 1 }],
     success_url: "https://example.com/success",
     cancel_url: "https://example.com/pricing",
     metadata: attribution,
     payment_intent_data: { metadata: attribution },
   });

   Recurring Stripe Checkout

   Copy

   1

   2

   3

   4

   5

   6

   7

   8

   9

   10

   11

   12

   13

   14

   // Subscription checkout uses subscription_data instead of payment_intent_data.
   const attribution = {
     metricraven_visitor_id: visitorId || "",
     metricraven_user_id: authenticatedUser.id,
     metricraven_plan: "pro_monthly",
   };
   const session = await stripe.checkout.sessions.create({
     mode: "subscription",
     line_items: [{ price: "YOUR_RECURRING_STRIPE_PRICE_ID", quantity: 1 }],
     success_url: "https://example.com/success",
     cancel_url: "https://example.com/pricing",
     metadata: attribution,
     subscription_data: { metadata: attribution },
   });

3. Identify signed-in users

   Call the Identify API when a visitor signs in, so later payments stay linked to that user.

Subscriptions and MRR

Revenue → Stripe subscriptions shows the current live state, separate from the selected payment dates. Estimated MRR includes active and past-due recurring prices after ongoing discounts.