Connector Improvement: Add support to ingest recurly "subscription history" export feature
AnsweredRecurly has this feature to export subscription history -- for context, this is a different subscription history compared to what is indicated in Recurly ERD. Our main use case for wanting to ingest this data is to solve the problem of subscription movement visibility.
Right now, with the existing history table in our warehouse (generated via fivetran recurly connector) requires a lot of effort to extract the specific subscription changes because it's blended with other updates such as billing invoices updates, account updates, etc. The only thing we're interested in right now is to have clear visibility on various subscription movements such as upgrades, downgrades, cancellations, trial conversions, etc.
Hence, why we wanted to ingest this via fivetran in the first place because it already captures the information that we want to see out of the box.
-
Official comment
Hi Ben,
Thank you for your feature request regarding the Recurly "subscription history" export. Currently, this feature is not on our immediate roadmap. However, I encourage you to upvote it in our feature request portal, as this will help us prioritise it based on user interest. We appreciate your input and will keep your request in mind for future consideration.
Best,
Sanjeevv Maniram
Please sign in to leave a comment.
Comments
1 comment