Connect Creem to SiteOps
Creem is a merchant of record built for small SaaS and indie products: it runs your checkout, handles VAT and sales tax in every country your buyers live in, and pays you out the remainder. It is deliberately small-team-shaped — one store, one dashboard, no enterprise maze — which is exactly why a lot of solo founders and small products run their billing on it. SiteOps treats it as a first-class revenue source, same footing as Stripe.
Connecting Creem puts your real revenue inside SiteOps, next to your traffic and your ad spend. A launch day, a price change, a campaign going live — you see whether it moved money on the same screen where you see whether it moved visitors, without flipping between the Creem dashboard and everything else.
The setup is the shortest of all the payment providers: Creem gives every store an API key in the Developers section, and you paste it into SiteOps. With that key SiteOps reads transactions and subscriptions — and reads is the whole story. It never creates charges, never edits plans, never touches a customer. Payments are read-only in SiteOps forever, by design.
Set it up, step by step
0 of 7 done
- Dashboard
- Developers
The store's key — into SiteOps and nowhere else - Settings
- Connections
- Creem
If something does not work
- The revenue card shows zero after connecting
- Two likely causes. First: you copied the test-mode key — switch Creem to live mode, copy the live key, and reconnect. Second: the store genuinely has no live charges yet, in which case zero is the honest number and the card fills in with your first sale.
- I rotated my Creem key — what do I do in SiteOps?
- Paste the new key over the old one in Settings. Rotation invalidates the old value the moment it happens, so SiteOps stops seeing new data until the fresh key is saved. History already synced stays where it is.
- The numbers do not exactly match my Creem dashboard
- Usually timing and definitions. SiteOps shows revenue by charge date in your project's time range; a payment dashboard may group by payout, treat refunds differently, or use another timezone. If the shape of the chart matches and the gap is small, the connection is fine.
- Can SiteOps change anything in my Creem store?
- No. SiteOps only ever reads from payment providers — there is no refund button, no plan editor, no code path that writes to Creem. Your billing stays entirely in your hands, and you can cut access at any moment by rotating the key.
- I want to disconnect — what happens to the data
- Rotate the key in Creem's Developers section or press Disconnect in SiteOps settings. Either way access stops immediately: SiteOps stops seeing new charges and the revenue card stops updating. Nothing in your Creem store is affected.