Skip to content
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

Open
aldesantis opened this issue Mar 5, 2021 · 4 comments
Open

Remove ChurnBuster integration #209

aldesantis opened this issue Mar 5, 2021 · 4 comments
Labels
removed Removes an existing functionality. stale

Comments

@aldesantis
Copy link
Member

aldesantis commented Mar 5, 2021

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.

@aldesantis aldesantis added the removed Removes an existing functionality. label Mar 5, 2021
@stale
Copy link

stale bot commented Jun 2, 2021

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.

@stale stale bot added the stale label Jun 2, 2021
@stale stale bot removed the stale label Jun 17, 2021
@garciajordy
Copy link

garciajordy commented Jun 17, 2021

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?
@aldesantis

@aldesantis
Copy link
Member Author

@garciajordy that's correct, we should remove all code and references for the ChurnBuster integration.

@stale
Copy link

stale bot commented Aug 18, 2021

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.

@stale stale bot added the stale label Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
removed Removes an existing functionality. stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants