Hey @Ayush @johnyeocx 👋🏻
Hey @Ayush @johnyeocx 
We’re using Autumn for payments at @LucidEditor and recently integrated Stripe webhooks to track plan changes for analytics. Wanted to get your thoughts on our current setup.
Here’s what we’re doing:
- For free users (attached to the Free product, which has no price), no Stripe subscription is created – we mark those users with
- When a user purchases a paid plan (Pro product), we treat
- When a user cancels, downgrades, or their plan expires, we treat
This allows us to track two events –
Would love to hear your thoughts:
1. Do you see any potential issues or edge cases with this approach?
2. Are there any simpler or more robust ways to handle this using Autumn?
Thanks!
We’re using Autumn for payments at @LucidEditor and recently integrated Stripe webhooks to track plan changes for analytics. Wanted to get your thoughts on our current setup.
Here’s what we’re doing:
- For free users (attached to the Free product, which has no price), no Stripe subscription is created – we mark those users with
"free" during onboarding.- When a user purchases a paid plan (Pro product), we treat
subscription.created as a plan upgrade and mark those users with"pro" .- When a user cancels, downgrades, or their plan expires, we treat
subscription.deleted as a plan downgrade and mark those users with"free .This allows us to track two events –
plan_upgraded and plan_downgraded – and group our users into paying and non-paying customers.Would love to hear your thoughts:
1. Do you see any potential issues or edge cases with this approach?
2. Are there any simpler or more robust ways to handle this using Autumn?
Thanks!
