A core action stops being recorded
If the action feeds a health score, missing activity can make an account look inactive.
Customer Success
The account needs help. Your list no longer shows it.
Say a release stops recording an account’s plan. Usage still arrives, but your Enterprise segment loses the accounts it can no longer classify. Skene checks the fields your health model depends on.
Free means one audit: sign in, connect a source, no card.
code
usage
account_plan
plan
health segment
1 unclassified
The signal still arrives, but its missing account plan leaves the segment unable to classify the account.
Keep segment requirements explicit
A required account field can be checked before it is used to define a segment.
Check the evidence behind usage
Finding a source does not establish recent activity. Read the evidence before using it in a health score.
You keep the health model
Your team defines what healthy means. A tracking review gives engineering a named event or field to inspect.
Two failures
Start freeTwo ways the list lies to you.
A missing usage event can make an account look inactive. A missing account field can exclude it from a segment altogether.
A field stops arriving
If the segment requires that field, the account may stop matching its rule.
Nothing stops firing. The list gets shorter.
For example, an update can stop sending an account’s plan with a usage signal. The event still arrives, but a segment that requires the plan can no longer classify the account.
Check the required field before changing the health model.
Missing and unverified evidence need different follow-up.
plan
setup_completed
event
account_id
user_id
plan
source
events + fields5/5
check
ReadyMissing details get caught with the change that drops them.
A tracking review gives engineering a finding it can inspect. This real, redacted review follows a missing event through a suggested fix and a later passing review.
Read the finding against the requirement your team depends on.
An unverified requirement remains distinct from a missing event.
check
1missing event
08:14 UTC
verdict
Passedlater review
09:20 UTC
Before the segment goes quiet
The flag is one signal. Its fields keep the account on the list.
Define the health measure and the fields it needs. Verification preserves each requirement, including one it has not yet been able to confirm.
plan
Trial activationtarget4.0%
required evidence
setup_completedaccount_id
Who owns whatYou decide Engineering does
What healthy means, and which fields your segments depend on.
Reviews the finding and the proposed fix.
Your team keeps ownership of the health model.