StoreMetrics Docs

StoreMetrics Docs

Search product docs or ask for an answer based on the docs.

Revenue

Stripe revenue

OAuth connect. Paid sessions and invoices. Metadata stitches humans to money.

Stripe revenue

Connect with OAuth — no paste-the-secret circus for the basic link.

Connect flow

  1. Settings → Integrations
  2. Connect Stripe
  3. Approve access
  4. Return to StoreMetrics
  5. Optionally pull historical payments

Events StoreMetrics cares about

  • checkout.session.completed
  • invoice.paid
  • charge.refunded

Normalized into the same purchase model as Shopify for the dashboard.

Attribution that actually works

When your app creates Checkout Sessions or PaymentIntents, attach:

const metadata = {
  velora_site_id: "YOUR_SITE_KEY",
  velora_visitor_id: readCookie("velora_visitor_id"),
  velora_session_id: readCookie("velora_session_id"),
};

Put the same object on metadata and, for Checkout, payment_intent_data.metadata.

Next.js example lives in Settings when platform is Next.js — or steal the prompt below.

Prompt — wire metadata

Update my Stripe Checkout / PaymentIntent creation so StoreMetrics can attribute revenue.

Set metadata velora_site_id, velora_visitor_id, velora_session_id from cookies
velora_visitor_id and velora_session_id. Site id is YOUR_SITE_KEY.

Show the diff only. Do not rotate Stripe keys. Do not log full card data.

Verify

  1. Complete a test Checkout in a browser that has the StoreMetrics script.
  2. Watch for a Purchase in the live feed.
  3. Open the actor — browsing should sit behind the payment when metadata was present.