Keeping track of subscription changes

[boryn]

The plan_subscriptions table shows the current state of the users' subscriptions, but we have no idea of their history. And this information is often very valuable.

Of course, someone would (at least should) keep track of the payments, but it does not give the full image of subscription changes.

I'd see this functionality inside the library itself, with a simple table plan_subscription_log with fields:

• id
• tag
• subscriber_type
• subscriber_id
• plan_id
• name
• price
• currency
• action
• timestamp

where action could be one of: 'trial_started' / 'renewed' (treated as well as started) / 'canceled'.

This way we could know what user did with their subscription, when they decided to upgrade/downgrade/renew/cancel, how long they were with us, did they have any gaps in the subscription, etc. It's often very valuable information for the support team.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bpuig]

I increased the stale period, because it was short, let's keep this going on.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[aeq-dev]

+1 Nice feature, any updates on this ? Thanks

[bpuig]

This is a one-man project, made personally, there is no company behind or economic interest, so thing will be done when they are done and if they are done. Hope you understand if a feature takes long or it is not made at all. Thanks

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.