#xmrcivicboix
1 messages · Page 1 of 1 (latest)
By upgrade and downgrade do you mean for subscriptions, or something else?
yes purely subscriptions
events API is great but limited to 30 days. We want to find an alternative to this
Unfortunately we don't have anything that stretches further back APU-wise.
Are these accounts that you are starting fresh with? I would say the best way to have this data would be to record it while it happens. Otherwise your ability to get it would be fairly limited when going back further than 30 days.
Still looking in to this but unfortunately I don't think we provide much here off the top of my head
we're currently using the charges api to build a historical timeline for users. However, it seems there are some limits to this.
Yeah, and you could look at canceled_at on each cancelled subscription to see exactly when each one cancelled to get some info there
Can you tell me what you are struggling to find out of the things that you listed? I am happy to help try to figure out what you can do to look here
Upgrades and downgrades are tough I am sure. The thing I can immediately think to do there would be iterate through invoices and see if the subscription items on the invoice changed from there
basically we're trying to capture churn, expansion, new business, churn and reactivation ... we have it working but comparing to the stripe dashboard is a bit off
we basically want to replicate this on our end
Can you define each of those for me? I have a some knowledge of them but not well enough to immediately put them in stripe terms
Actually can you just define expansion and churn for me?
expansion is when the user upgrades from lower plan to a higher plan ... or, if the user already has one subscription but adds another subscription
churn is when a user cancels a subscription
Gotcha, I think canceled_at on the subscription object should help for churn then though that would include all the time until the subscription was cancelled. So for example if a user doesn't cancel their customer's subscriptions until they go a week without payment canceled_at would be the end of that week. https://stripe.com/docs/api/subscriptions/object#subscription_object-canceled_at
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
My immediate idea for upgrades and downgrades would be to go through each invoice for each subscription for each customer. You can see which invoice items are there from a subscription item which would tell you what the subscription looked like as each invoice happened. So that should give you a good timeline there albeit that would take a good amount of effort https://stripe.com/docs/api/invoices/line_item#invoice_line_item_object-subscription_item
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
does the invoice api return a historical list of action that happens for a subscription?
It does not, but it provides enough info to figure out what happened retroactively here
another question ... for each charge .. there seems to be a description of Subscription creation or Subscription update
is this reliable?
Yes though it is possible for a user to change the descriptions I believe. So for certain users they wouldn't have those exact subscriptions on each charge
Correct