Connect Gumroad to SiteOps

A creator grows two things at once: an audience, and the products that audience buys. The follower count is only half the story — the other half is what those downloads, presets and memberships actually earn on Gumroad. Without a read on it, SiteOps could show Maya her subscribers climbing while the revenue that pays for the work stayed invisible.

Connecting Gumroad to SiteOps puts product revenue next to the audience you're building, read-only. Sales sit beside your followers and subscribers, so a launch that moved money reads differently from a post that only got likes — and you can tell which channel grows the audience that actually buys.

It reads sales and nothing else. SiteOps never touches a product, a payout or a customer. Disconnect and the reads stop the same minute.

A read-only token — where it lives, and where it goes in SiteOps

Set it up, step by step

0 of 4 done

    1. Settings
    2. Advanced
    3. Applications
    1. Settings
    2. Connections
    3. Gumroad

If something does not work

Sales aren't showing up
Check the connection reads Connected and the token belongs to the account that sells these products. A token from a different Gumroad account will connect but read nothing.
The revenue differs from my Gumroad dashboard
Gumroad reports gross and net differently (fees, refunds, chargebacks settle over time), and SiteOps reads on a short delay. Compare a closed period rather than today, and the numbers line up.
Can SiteOps change a product or a price?
No — by construction. The token is read-only; there is no code path that edits a product, a price, a payout or a customer. SiteOps reads sales so you can see the return, nothing more.
I sell on Lemon Squeezy or Ko-fi, not Gumroad
This guide covers Gumroad specifically. Other creator-store connectors follow the same read-only shape as they're added; for now, if your store exposes a Stripe account, connecting Stripe reads the same revenue.

Set up once, see everything every morning

Get started