Why connect Stripe?
Cancellations tell you what's not working. When customers leave, they often say why, and those reasons are gold for product teams.
When you connect Stripe, ProductBet captures subscription cancellation reasons and turns them into signals. Over time, patterns in churn reasons surface as opportunities.
What gets captured
ProductBet listens for Stripe events and extracts:
- Cancellation reasons - why customers ended their subscription
- Payment signals - subscription changes and churn patterns
Each event becomes a signal linked back to the Stripe context.
How to connect
Go to Settings > Integrations > Stripe and follow the OAuth flow to authorize ProductBet. You're redirected back and the integration is active.
How it works
Once connected, Stripe sends webhook events to ProductBet whenever a subscription is cancelled or changes status. ProductBet processes the cancellation reason (if provided) and creates a signal.
What to expect
- Cancellation reasons often highlight UX friction, missing features, or pricing concerns
- When the same cancellation reason appears repeatedly, it surfaces as an opportunity
- Combining Stripe signals with Intercom and Slack signals gives you a complete picture of churn
Troubleshooting
- Not seeing signals? Cancellation signals only appear when customers cancel their subscriptions. If you don't have recent cancellations, you won't see signals yet.
- Cancellation reasons are vague? The quality of signals depends on the reasons customers provide when cancelling. If your Stripe checkout doesn't ask for a cancellation reason, consider enabling that in your Stripe billing settings.