Signals
Signals in SaaS Tracker are revenue-aware customer signals at the customer organization level. They combine:
- recent usage data (events and activity per customer_org_id)
- the organization’s health score
- revenue (MRR from subscriptions)
The goal is to highlight organizations that are worth immediate attention – whether because they are at risk or because they are growing fast.
Open Analytics → Signals to see a prioritized list of organizations with active signals.
How signals work
For each application, SaaS Tracker periodically scans customer organizations that have either:
- active revenue (subscriptions), or
- recent usage activity.
During the scan, it computes usage windows, health scores, and current MRR, then evaluates conditions for each signal type. When a condition is met, an active signal is stored for that organization.
Signals are always organization-level:
- one organization can have multiple active signal types at the same time
- you see one row per organization in the Signals view, with all its current signal types
Signal types
Revenue at risk
A Revenue at risk signal means that an organization with MRR shows low health.
Typical conditions include:
- the organization has MRR > 0
- the health score is below a low threshold (e.g. < 40 in the default model)
This usually indicates that engagement has dropped or usage is concentrated in a narrow set of features.
How to interpret:
- Treat these organizations as retention risks.
- Check their last activity, feature usage, and subscription size.
- Decide whether to reach out via customer success or account management.
Usage drop
A Usage drop signal means that the organization’s recent usage has fallen significantly compared to the previous period.
Typical conditions include:
- the organization has MRR > 0
- events in the last 30 days are much lower than in the previous 30 days (for example, < 70% of the previous period)
How to interpret:
- These customers used to be more active but usage is trending down.
- Combine the signal with health score and last seen to see if this is an early warning or part of a seasonal pattern.
Inactive paying
An Inactive paying signal means that the organization is paying but not recently active.
Typical conditions include:
- the organization has MRR > 0
- there has been no recent activity for a number of days (for example, > 14 days)
How to interpret:
- These are customers who may be at risk of silent churn.
- It is often worth checking whether they are stuck in onboarding, have moved to another tool, or have changed ownership internally.
Expansion candidate
An Expansion candidate signal means that a healthy organization is growing its usage noticeably.
Typical conditions include:
- the organization has a high health score (e.g. ≥ 80)
- usage in the last 30 days is substantially higher than in the previous 30 days
How to interpret:
- These customers are seeing value and using the product more over time.
- They are good candidates for expansion, upsell, or advocacy (case studies, references).
Priority
Signals are sorted by a priority score. The score is revenue-aware: organizations with higher MRR usually surface higher when the underlying risk or opportunity is meaningful.
In the Signals view you see:
- Priority – the highest signal score for the organization
- MRR – the MRR associated with the highest-priority signal
- Signals – all active signal types for the organization
- Primary reason – the explanation for the top signal
- Last seen – when the organization last had activity
- Detected – when the most recent signal for that org was detected
This lets you sort and scan the list quickly based on impact.
Dismissed signals
When you dismiss a signal in the UI, it is marked as dismissed and removed from the active list. Dismissed signals are not re-shown as active until a new scan would create a fresh signal that meets the conditions again.
Dismissing signals is useful when:
- you have already investigated the situation
- the signal is expected (for example, a planned pause)
- you want to keep the active list focused on open items
How to use signals
A practical workflow for using Signals:
- Start with the highest-priority organizations. Begin at the top of the list; these combine higher MRR with strong signal conditions.
- Review last seen and health. Check whether the organization is just slightly down or has been inactive for weeks.
- Open the organization detail page. From the Signals list, go to the organization detail to see timelines, subscriptions, and usage.
- Decide the case type:
- Risk – low health, usage drop, or inactive paying
- Onboarding / activation – imported orgs with revenue but low or no usage
- Expansion – expansion candidates with strong and growing usage
- Take action and optionally dismiss. After you have handled the case, you can dismiss the signal so that the list reflects remaining open items.