Connect Stripe
Connecting Stripe is what turns on every revenue feature: the metrics, the conversions list, and the link between a payment and the visit that drove it. You connect Stripe per site, so each site reports its own revenue.
It takes a minute: create a restricted key in Stripe, paste it into the site’s integration settings, and Snow handles the rest.
Use a restricted key (it starts with rk_…), never your secret key (the one
that starts with sk_…). A restricted key lets you grant read-only access to just
the data Snow needs, so you stay in control.
Create a restricted key in Stripe
In the Stripe Dashboard, go to Developers → API keys and create a new restricted key. Give it read access to the resources Snow reads:
- Charges: read
- Customers: read
- Subscriptions: read
- Invoices: read
You don’t need to grant write access to anything. Snow only reads your data.
Stripe restricted keys look like this:
rk_live_51AbCdEf... # live mode
rk_test_51AbCdEf... # test modePaste it into your site’s integration settings
Back in Snow, open the site’s integration settings and paste the restricted key. Snow encrypts the key at rest before storing it, so the raw key is never kept in plain text.
Snow imports your revenue
As soon as the key is saved, Snow connects to Stripe and imports your payments and subscriptions. Your revenue metrics and conversions list start filling in. From here on, Snow keeps everything current automatically. See how revenue stays up to date.
Test mode vs. live mode
Stripe keys come in two flavours:
- Live keys (
rk_live_…) read your real, live payments and subscriptions. - Test keys (
rk_test_…) read only your Stripe test data, handy for trying things out before you go live.
Connect the one that matches the data you want to see. To switch from test to live later, create a live restricted key and paste it in the same place.
Next step
A payment shows up in Snow on its own. To link that payment back to the visitor and source that drove it, set up attribution.