Overview
The Polar integration allows you to automatically track customer cancellations from your Polar subscriptions. When a customer cancels their subscription, SeggWat captures the event along with the cancellation reason and any comments they provide.This integration connects your Polar account to SeggWat. It tracks cancellations from your customers’ subscriptions, helping you understand why customers churn.
Features
- Automatic churn tracking - Cancellation events are captured in real-time via webhooks
- Cancellation reasons - See why customers are leaving (too expensive, missing features, etc.)
- Customer comments - Capture verbatim feedback from departing customers
- Churn analytics - View trends, statistics, and breakdowns in the Insights dashboard
- Owner notifications - Get notified when customers leave feedback with their cancellation
Setup Instructions
Step 1: Open the Polar Integration
- Navigate to your project in SeggWat
- Go to Integrations in the sidebar
- Click on the Polar integration card
Step 2: Copy the Webhook URL
In the Polar integration modal, you’ll see a unique webhook URL for your project:Step 3: Configure Polar Webhook
- Open your Polar Dashboard
- Go to Settings → Webhooks
- Click Add Endpoint
- Paste the webhook URL from SeggWat
- For Format, select Raw (important!)
- Under Events, enable:
subscription.canceled
- Click Create
Step 4: Copy the Webhook Secret
After creating the webhook in Polar:- Click on the webhook you just created
- Copy the Webhook Secret (starts with
polar_whs_) - Return to SeggWat and paste it in the Webhook Secret field
- Click Save Secret
Viewing Churn Data
Once configured, churn data appears in two places:Insights → Churn Tab
Navigate to Insights and click the Churn tab to see:- Total cancellations - All-time count
- Monthly trends - This month vs. last month with percentage change
- Cancellation reasons - Visual breakdown of why customers churn
- Recent cancellations - List of recent events with customer details and comments
Notifications
Project owners receive notifications when customers include comments with their cancellations. This helps you quickly respond to actionable feedback.Cancellation Reasons
Polar captures standardized cancellation reasons that SeggWat maps to the following categories:| Reason | Description |
|---|---|
| Too Expensive | Customer finds the price too high |
| Missing Features | Product lacks features the customer needs |
| Switched Service | Customer moved to a competitor |
| Low Quality | Customer is unhappy with product quality |
| Too Complex | Product is too difficult to use |
| Unused | Customer no longer needs the product |
| Customer Service | Issues with support experience |
| Other | Custom reason provided by customer |
Troubleshooting
Webhook Not Receiving Events
- Verify the webhook URL is correct in Polar
- Ensure the webhook secret matches (starts with
polar_whs_) - Check that
subscription.canceledevent is enabled - Confirm the webhook format is set to Raw
Integration Shows “Pending”
The status changes to “Active” after the first successful webhook is received. You can:- Wait for a real cancellation
- Use Polar’s webhook testing feature to send a test event
Invalid Secret Error
If you see a secret validation error:- Re-copy the secret from Polar (click to reveal the full secret)
- Ensure no extra spaces before or after the secret
- The secret should start with
polar_whs_
Data Privacy
SeggWat only stores:- Subscription ID (for deduplication)
- Customer ID and email (if provided by Polar)
- Cancellation reason and comment
- Timestamp and product name