Essential events: trial_started, subscription_purchased, subscription_renewed, subscription_canceled, payment_failed, refund_processed, and subscription_expired. Each should trigger an appropriate backend action and/or CRM campaign.
Implement retry logic: if your server does not return a 200 response, the webhook sender should retry (Botsi retries automatically). Log all incoming webhooks for debugging. Implement idempotency (handle duplicate deliveries gracefully). Set up monitoring to alert you if webhook processing fails.
Botsi handles most subscription management internally, but webhooks let you sync events with your own backend, CRM, data warehouse, and other systems. They are optional for basic subscription management but essential for advanced lifecycle marketing and custom business logic.
A subscription purchased through a website (commonly using Stripe or Paddle) instead of in-app purchase systems. Web subscriptions allow apps to avoid platform fees and offer more flexible pricing or promotional options.
The process of converting users from a web page, landing experience, or email into app installers, and eventually subscribers. Optimizing this flow requires deep linking, continuity of messaging, and frictionless onboarding.
The number of unique users who engage with the app within a 7-day period. WAU is a useful middle-ground metric between DAU and MAU, and is often tied to user health scoring and retention tracking.
The onboarding sequence shown to new users, often guiding them through feature highlights, value communication, and eventually a paywall or trial prompt. A strong welcome flow increases trial starts and early retention.
An app developed once but branded and resold by multiple companies or partners. Common in fitness, education, or wellness categories where the core functionality is the same, but the front-end branding and messaging differ.
Botsi automatically shows the right price to every user. Stop guessing and start growing.