Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Stripe -> subscription_item not loading historical data

Answered
Rodrigo User
  • Edited

Hi there,

Basically FiveTran is not loading subscription_item historical data but instead it is only fetching the current subscription_item of a subscription. But, this data is very important for us at the moment and we used to get it from Stitch.

Is it possible for us to get the historical data too?

Thanks in advance

Please sign in to leave a comment.

Comments

7 comments

Date Votes
  • Official comment
    Bjorn User
    • Edited

    Hi Rodrigo, this is unlikely to happen. We decide where we keep the history at the time we are building the connector, but usually don't add this once the connector is generally available. 

  • Anna User

    Hi Rodrigo, I'm interested in learning more about this request. What are some of the use cases you have for this historical data on subscription_item? 

  • Rodrigo User

    Hi Anna,

    Our main use case for this data is to build dashboards that track MRR changes in our subscriptions.

    If we had a client on a $500 subscription and the subscription was updated so that the new price is $700, we would like to know that the MRR changed positively $200.

    What happens now is that only the newest active subscription_item appears ($700 one) on our Warehouse and previous subscription_item ($500) is hard deleted instead of soft deleted.

  • Anna User

    Thanks Rodrigo! We've received enough requests for this to add the feature to our backlog– I will let you know when it is available.

  • Lukas Köbis User

    Any updates here? Looks like there's subscription_history but no subscription_item_history.

  • Tyler Larsen User

    Any updates here? This is a huge issue for us, too. We'll likely start syncing this data via custom pipeline, but I would much rather be able to do this via fivetran.

  • Elise Eagan User

    Echoing the above- this is a major issue for us as well for the same reasons. Is this work still in the backlog?