Track canceled subscriptions in your Ruby application

LogSnag makes it easy to track your Ruby application and monitor when a user cancels their subscription.

Many Ruby applications have a subscription model where users pay a monthly or yearly fee to use the application. These applications are called SaaS or Software as a Service application. In these applications, users are usually charged a monthly or yearly fee and can use the application for that period. In some cases, users are on a pay-as-you-go model set for each action they perform in the application.

In either of these cases, a common issue that the application usually faces is when a user cancels their subscription, also called churn. Therefore, an application's churn rate is a critical metric that can significantly affect the application's revenue and, consequently, the sustainability of the application.

Therefore, SaaS applications should actively monitor when users cancel their subscriptions, the reason for the cancellation, and the overall churn rate. This way, the application can always be aware of the performance of the application and take immediate action if needed. For example, in the case of a high churn rate, the application can take action to improve the user experience to reduce churn. Or, in the case of a high-value user canceling their subscription, the application owner can take action to retain the user.

LogSnag is a powerful, real-time event tracking tool that works seamlessly with any Ruby application and is an excellent solution for tracking subscription cancellations and churn rates. With LogSnag, you can set up event tracking for anything you want and track when users cancel their subscription in your Ruby application in real-time. You may also set up optional rules to notify you and your team when a user has canceled their subscription.

In addition, LogSnag allows you to track user journeys and create a timeline of events for each user. This way, you can always track the activity of a specific user, such as when they have canceled their subscription and any other activity they have done in your application.


Setting up LogSnag

  1. Sign up for a free LogSnag account.
  2. Create your first project from the dashboard.
  3. Head to settings and copy your API token.

Ruby code snippets

To track subscription cancellations in your Ruby application, you can use the following code snippet. Please replace the YOUR_API_TOKEN with your API token and update the project and channel names.

Using Ruby with Net::HTTP
require "uri"
require "json"
require "net/http"

url = URI("https://api.logsnag.com/v1/log")

https = Net::HTTP.new(url.host, url.port)
https.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Content-Type"] = "application/json"
request["Authorization"] = "Bearer YOUR_API_TOKEN"
request.body = JSON.dump({
  "project": "my-saas",
  "channel": "billing",
  "event": "Subscription Cancelled",
  "description": "User cancelled a startup subscription",
  "icon": "🛑",
  "notify": true
})

response = https.request(request)
puts response.read_body

Ruby integration details

We believe that event tracking should be simple and accessible to every developer and team. Therefore, we have worked hard to create the next generation of event tracking tools. As a result, LogSnag is flexible and easy to use, making it a great companion for your Ruby applications.

In addition to real-time event tracking, LogSnag provides powerful features such as cross-platform push notifications, event filtering, user and product journeys, charts, insights, and more.

LogSnag provides a generous free plan to get you started with event tracking. You can also check out our pricing page to see our paid plans. So don't hesitate to give us a try and let us know what you think!

Other use-cases for LogSnag

  1. Track payment events via Ruby

  2. Track user signup events via Ruby

  3. Track your Ruby cron jobs

  4. Track waitlist signup events via Ruby

  5. Track user sign in events in Ruby

  6. Get a notification when your Ruby code is done executing

  7. Monitor when a user exceeds the usage limit for your Ruby service

  8. Monitor when a new feature is used in your Ruby application

  9. Monitor suspicious activity in your Ruby application

  10. Monitor when a user is being rate limited in your Ruby application

  11. Monitor when database goes down in your Ruby application

  12. Monitor your CPU usage in your Ruby application

  13. Monitor memory usage in your Ruby application

  14. Monitor high disk usage in your Ruby application

  15. Track when a file is uploaded to your Ruby application

  16. Track when a form is submitted to your Ruby application

  17. Monitor failed payments for your Ruby application

  18. Monitor your CI/CD build status for your Ruby application

  19. Monitor when a user changes their email address in your Ruby application

  20. Monitor Redis downtime in your Ruby application

    View all common use-cases with Ruby