ChurnRadar Back to home
QUICK START

Connect your product to ChurnRadar

Send product events from your backend, create an API key, and review daily churn-risk scores in a simple workspace.

1. Create your account and workspace

  1. Sign up and verify your email.
  2. Choose a paid plan or ask about cryptocurrency payment on the pricing page.
  3. Open the dashboard and create an API key for your production or staging environment.
  4. Keep the key in a server-only environment variable. Never expose it in browser code or source control.

2. Send product events

Send one request per meaningful product action. Use stable IDs and keep metadata small. Do not send passwords, payment data, secrets, or sensitive personal information.

POST /api/v1/track
await fetch("https://everflow-ai-backend.onrender.com/api/v1/track", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-Key": process.env.CHURNRADAR_API_KEY,
  },
  body: JSON.stringify({
    customerId: "acme-123",
    customerName: "Acme Corp",
    userId: "user_456",
    eventType: "feature_used",
    metadata: { feature: "reports", mrr: 500 },
  }),
});

Required fields

  • customerId: your customer/account ID.
  • userId: the product user ID.
  • eventType: a short event name such as feature_used.

Optional fields

  • customerName: display name for the account.
  • metadata: event JSON with extra context, kept small and non-sensitive. Its optional mrr field must be a number from 0 to 1,000,000.
  • customerMetadata: optional account-level JSON object. Its mrr field accepts the same numeric range; when both MRR fields are sent, metadata.mrr takes precedence.
  • occurredAt: event timestamp if you want to send a historical event.

MRR is stored with the account and updated by later events. Use the same currency for all MRR values in a workspace; ChurnRadar stores the numeric amount but no currency code. The dashboard ranks at-risk accounts by MRR, then risk score, and totals MRR for accounts scoring 50 or more.

Send the X-API-Key header from a trusted server. A successful request returns 202. Invalid requests return 400; oversized payloads return 413; bad or revoked keys return 401; inactive subscriptions return 402; 429 indicates too many requests (more than 600 events per minute per API key).

3. Review your churn scores

ChurnRadar recalculates customer scores daily. It compares recent product activity to a baseline and looks at how long it has been since the last meaningful event. Scores run from 0 to 100. The dashboard marks scores of 50 or more as at risk.

For each account, the dashboard explains recent 14-day event activity against its average per-14-day activity over the preceding 46 days, along with time since the last event. Its timeline groups the last 46 days into six weekly periods and one oldest four-day period; the latest 14 days are highlighted.

This is an activity-based heuristic, not a validated prediction of churn. A brand-new account or sparse event stream can produce noisy results. Always review the score with your own sales or customer success context.

Use Draft a message on an at-risk account to create a draft on demand. When an OpenAI key is configured, the action requests an AI-generated draft; otherwise it provides a non-AI template. AI drafts are labeled “review before sending.” Drafts can be edited and copied, and ChurnRadar never sends them.

4. Use the Retention Playbook

Active subscribers can open the Retention Playbook from the dashboard. It includes ready-to-edit, copyable email templates for quiet accounts, declining usage, abandoned features, departed champions, and long-silent customers. These are manual templates; ChurnRadar does not independently detect abandoned features or champion changes.

5. Record customer outcomes

For an account currently marked at risk, choose contacted, saved, churned, or ignored and optionally add a note. The dashboard’s saved-account and saved-MRR totals are user-entered outcomes, not independently verified results.

6. Optional daily email digest

When Resend is configured for the service, signed-in subscribers can opt in from the dashboard. The digest is sent to the account email after daily scoring, includes up to five at-risk accounts, and has a signed unsubscribe link that works without signing in. Email delivery is disabled unless configured and is off by default for each account.

Security and account controls

  • Workspace and API routes require a signed-in user and an active subscription.
  • API keys are hashed, shown once, and can be revoked from the dashboard.
  • Use HTTPS in production and keep server secrets in your hosting environment.
Open workspace