Integrations
Connect customer signals to Churnor
Receive billing changes from Stripe, Paddle, and Dodo Payments. Send product activity through the Events API, or import an existing customer list with CSV.
Stripe
Receive supported subscription and payment changes through signed provider webhooks. Configure the endpoint for your product environment and verify a processed delivery.
Subscription and payment events to select
customer.subscription.createdcustomer.subscription.updatedcustomer.subscription.deletedinvoice.payment_failedinvoice.payment_succeeded
Paddle
Automatically import existing customers and subscriptions with a provider API key, then receive changes through signed webhooks. Imports continue in the background without cron jobs. Configure the endpoint for your product environment and verify a processed delivery.
Subscription and payment events to select
subscription.createdsubscription.updatedsubscription.canceledsubscription.past_duesubscription.pausedsubscription.resumedtransaction.payment_failedtransaction.completed
Dodo Payments
Automatically import existing customers and subscriptions with a provider API key, then receive changes through signed webhooks. Imports continue in the background without cron jobs. Configure the endpoint for your product environment and verify a processed delivery.
Subscription and payment events to select
subscription.activesubscription.updatedsubscription.plan_changedsubscription.cancelledsubscription.expiredsubscription.past_duesubscription.on_holdsubscription.pausedsubscription.unpausedsubscription.renewedsubscription.failedpayment.failedpayment.succeeded
Events API
Send customer activity from your backend with Bearer API key authentication. Single-event and batch endpoints accept standard JSON, with optional stable identifiers for duplicate handling.
CSV import
Import existing customer records in the dashboard and map your columns. Use the same external IDs as your product events and billing records.
Send product activity with HTTP
This is an illustrative server-side request. Keep the key in your backend and choose a stable customer identifier that matches your other data sources.
// Run on your server; do not expose the key in browser code.
const response = await fetch("https://churnor.vercel.app/api/v1/events", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.CHURNOR_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"customer_id": "example_customer",
"event": "report_exported",
"idempotency_key": "example_delivery_1",
"properties": {
"format": "csv"
}
}),
});
if (!response.ok) throw new Error(`Churnor returned ${response.status}`);
const result = await response.json();Verify an actual delivery
Creating an API key or saving a provider secret does not establish that events are arriving. Deliver a supported event and check its processing status in Churnor. Paddle and Dodo import existing customers and current subscriptions when connected; import completion and signed delivery verification are shown separately. Use the Events API for product activity, and CSV for initial Stripe records.
Scoring follows event delivery and refreshes on authorized dashboard reads when assessments are older than 24 hours. No background inactivity scan runs while the application is unused.
Setup and monitoring guides
Choose a guide for the data you want to connect or the customer workflow you want to review.
- Stripe Integration Setup Guide
Connect Stripe subscription and payment events to Churnor. Configure signed webhooks, match customer IDs, and verify a supported event delivery.
- Paddle Integration Setup Guide
Connect Paddle Billing to Churnor with signed webhooks. Learn supported events, customer matching, revenue limitations, and delivery verification.
- Dodo Payments Integration Setup Guide
Connect Dodo Payments customer billing data to Churnor. Set up signed webhooks, supported events, customer matching, and delivery verification.
- CSV Customer Import Guide for Churn Monitoring
Prepare a customer CSV for Churnor, map external IDs and supported fields, review import results, and learn when to use the Events API instead.
- A Practical Guide to SaaS Churn Monitoring
Learn how to bring product activity and billing changes together, review customer risk evidence, and prioritize follow-up with Churnor.
- Customer Event Tracking for SaaS Churn Monitoring
Choose meaningful product events, send them to Churnor’s Events API, and understand how event names, timestamps, and customer IDs are used.
- Match Customer IDs Across Billing and Product Events
Keep a stable external customer ID across Churnor’s Events API, CSV imports, Stripe, Paddle, and Dodo Payments.