Gumroad analytics: revenue by channel
ProductLense connects to Gumroad and attributes every payment, refund and renewal to the channel, campaign and landing page that first brought the customer. Gumroad sales and memberships, with Gumroad’s fee and refund and chargeback flags.
Setup steps
- In Gumroad, open Settings → Advanced → Applications, create an application and generate an access token.
- In ProductLense, open Settings → Billing connections → Gumroad and paste the token.
- In Gumroad → Settings → Advanced, set the Ping URL to the URL ProductLense shows after you save.
- ProductLense backfills 12 months of sales.
Credentials and permissions
| Field | Secret | Where to find it |
|---|---|---|
| Access token | Yes, encrypted at rest | An OAuth access token from an application with the view_sales scope (Settings → Advanced → Applications). |
Webhook
URL pattern, shown with your connection id after you save:
https://api.productlense.app/api/webhooks/gumroad/{connection_id}Events: sale, refund, dispute, cancellation, subscription_updated
Verification: Gumroad pings are unsigned, so ProductLense re-fetches the sale or subscriber from the API before trusting it.
What ProductLense reads
- Customers
- Buyer email from each sale.
- Subscriptions
- Memberships, from sales and subscriber pings.
- Payments
- Sales.
- Refunds
- Refunded and chargeback flags (full price).
- Fees
- The Gumroad fee on each sale.
What ProductLense never touches
- Never creates, changes, refunds or cancels anything: read-only API calls and incoming webhooks only.
- Never moves money, issues payouts, or reads bank account details.
- Never sees full card numbers; providers do not expose them.
- Never sends your customer data to the AI model: Ask and the daily insight see aggregates only.
Match payments to your users
Add a custom field named pl_user_id to the product to match by id. Without it, ProductLense matches by buyer email, so include the email in your identify traits.
Product → Checkout → Custom fields → add a field named pl_user_id.
Without it, ProductLense matches the sale to your identify call by buyer email.Gumroad and ProductLense: questions
- Does ProductLense work with Gumroad?
- Yes. ProductLense connects to Gumroad with access token, backfills 12 months of history, and stays current through signed webhooks plus a nightly reconcile. One connection is included on Starter; Growth and Scale allow every provider at once on the same site.
- What data does ProductLense read from Gumroad?
- Customers, subscriptions, payments, refunds and fees, read-only. Payments: sales. Refunds: refunded and chargeback flags (full price). Fees: the Gumroad fee on each sale.
- Can ProductLense change anything in my Gumroad account?
- No. ProductLense only makes read calls and receives webhooks. It never creates, changes, refunds or cancels anything, never moves money, and never sees card numbers. Credentials are encrypted at rest, and the AI features only ever see aggregated numbers, never your customers’ data.
- How does ProductLense match Gumroad payments to visitors?
- Add a custom field named pl_user_id to the product to match by id. Without it, ProductLense matches by buyer email, so include the email in your identify traits. Your site calls identify with the same user id after signup, and ProductLense follows the payment to that visitor’s first touch: source, medium, campaign and landing page.
- Are Gumroad fees subtracted from revenue?
- The Gumroad fee on each sale. Net revenue is the charge minus the fee; refunds subtract the refunded amount and its fee. Profit per channel then subtracts ad spend.
Connect Gumroad and see revenue by channel today.
Add the script, connect Stripe or any of 14 other billing providers, and see revenue by channel the same day.