Churn.io offers two ways to deliver your cancel flow to customers: as an embedded widget or as a hosted cancel page. Both support the same flow steps, offer types, and analytics. The difference is purely in how and where the experience is delivered. This article helps you choose the right one for your business.
Side-by-side comparison
Widget | Cancel Page | |
Delivery | Modal overlay on your site | Full-page redirect |
Customer stays on your site | Yes | No (redirect) |
Code required on your site | Script tag + JS trigger | Backend token generation |
Works in emails or external links | No | Yes |
Custom domain | N/A | Yes (Pro) |
Full-page branding control | Modal only | Full page |
Choose the widget if...
Your cancel button lives inside your app or dashboard
You want the experience to feel native to your product without a redirect
Your team has access to the frontend codebase to add a script tag and JS call
Choose the cancel page if...
Customers cancel from a billing portal, email link, or Stripe-hosted page
You want to get started without touching your frontend code
You prefer a full-page immersive experience over a modal
✅ You can use both at the same time
There is no need to choose just one. Many customers run a widget inside their app and a hosted cancel page for billing emails simultaneously. Both appear as separate flows in your dashboard with their own analytics.
💬 Questions or concerns?
Get help from our support specialists at Churn.io. Click the chat icon at the bottom of your screen to reach us directly.