An event tracking tool for the signals that change your SaaS.
Not every click. The signups, upgrades, cancellations and errors that actually move your SaaS – sent once, over one HTTP call, and turned into alerts, a feed, metrics and charts.
What counts as an event, and what doesn't
An event is one meaningful thing that happened: a signup, a payment, a cancellation, a business error. Name it as a stable fact, not a UI action – "subscription.upgraded" survives a redesign, "clicked upgrade button" doesn't. This is different from logs, which are for debugging and disappear after a retention window, and different from click tracking tools like GA4, which capture every interaction by default. Here, you decide what matters, once.
Events worth tracking for an early-stage SaaS
- Signup – a new account is created.
- Activation – a user reaches the first moment of real value.
- Upgrade or downgrade – a customer changes plan.
- Cancellation – a subscription ends.
- Payment failed – a charge or renewal doesn't go through.
- Business error – a workflow fails in a way that affects a customer.
One HTTP call. No SDK to install.
Give the event a stable title, attach the properties you'll want to filter or chart on later, and optionally link it to a user.
$ curl -X POST https://api.logsninja.com/v1/events \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -d '{ "project": "YOUR_PROJECT_ID", "stream": "billing", "title": "subscription.upgraded", "emoji": "🚀", "metadata": {"plan": "pro"}, "user": "user_123", "notify": true }' ✓ Event received ✓ Push sent to 1 device # feed, metric and chart updated
The same event becomes
Before you ship
- Sensitive data – never send full card numbers, passwords, or tokens as event properties.
- Environments – keep staging and production events in separate projects, not mixed in the same one.
- Taxonomy – agree on a naming convention as a team before events pile up under inconsistent names.
Frequently asked questions
Is this the same as event tracking in GA4?
No. GA4 is built for marketing and page-level behavior, and captures interactions broadly. LogsNinja is built for the events that change your business – you send fewer, more deliberate events, and each one can also trigger a native alert.
How many events should I send per day?
As many as reflect real business activity. There's no benefit to tracking every click – start with the six events above and add more only when you have a specific question to answer.
Can I attach custom properties to an event?
Yes, through the metadata field. Use it for anything you'll want to filter, group or sum later, like plan, amount or region.
Do I need to install anything?
No SDK. Events are sent with a single HTTP call, so any language or framework that can make a request can send them.
Send the event that matters most right now.
See it become an alert, a feed entry, a metric and a chart – in seconds.