-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove ChurnBuster integration #209
Comments
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions. |
So basically the best thing to do is to change the code to how it was before the ChurnBuster integration? Or am I missing something? |
@garciajordy that's correct, we should remove all code and references for the ChurnBuster integration. |
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions. |
Integrating solidus_subscriptions with ChurnBuster seemed like a good idea, but the reality is that it's impossible to make the two work well together: ChurnBuster works well when it's integrated with a natively-supported platform such as Shopify/ReCharge. When that's the case, ChurnBuster can manage the subscriptions directly (e.g., by cancelling them after sending the churn recovery email sequence).
When ChurnBuster is integrated with Solidus and Solidus initiates ChurnBuster campaigns, the timing of emails going out in ChurnBuster and Solidus taking actions such as cancelling the subscription would need to be perfectly synchronized (i.e. Solidus would need to cancel the subscription right when ChurnBuster sends the "subscription cancelled" email). This is impossible to achieve in the real world, which leads to a subpar UX.
Churn recovery with solidus_subscriptions is better done with other services or other third-party tools, but ChurnBuster is definitely not a good option.
My suggestion is to simply remove the integration in the next major version with no deprecation in between.
The text was updated successfully, but these errors were encountered: