For Customer Success
Check the events behind a health score before you act on it.
Your team defines account health, and engineering ships the product events it reads. Skene checks those events and fields, so a missing event is not read as low usage.
A real answer / Skene’s own workspace
Skene named five retention events missing from our own code.
See if tracking can answer it.
Ask a question. Skene names what is missing.
- Marketing ops
- Sales ops
- CS ops
- Product ops
- RevOps / GTM ops
- Data ops
- Can we tell whether a workspace has a defined activation path and a completed activation run?
- Can activation goals be joined to the workspace they belong to?
- Can tracking support a path from onboarding activity to activation completion?
I want to increase retention with our customers
14 investigation steps
To answer this question we need the following events:
| Event | Why | Parameters | Status |
|---|---|---|---|
first_ | This marks when an account reaches the product outcome, which is the key point to measure retention from. | plantimestamp | Not found |
feature_ | This shows which parts of the product customers keep returning to after activation. | featureplantimestamp | Not found |
onboarding_ | This identifies where customers stop during setup, which helps find early drop-off that hurts retention. | steptimestamp | Not found |
subscription_ | This captures churn directly so you can measure how retention changes over time. | plantimestamp | Not found |
support_ | This helps connect support issues to later churn or repeated use patterns. | timestamp | Not found |
Review the missing event
Give engineering the event and the reason it matters.
- 01 / Skene
Names the evidence gap
support_ticket_openedis missing, so support issues cannot be tied to later churn. - 02 / Coding agent
Prepares the tracking change
Follows the How to fix brief: add the event where tickets are created and send a timestamp.
- 03 / Engineering and Skene
Review and check again
Engineering reviews the change. Skene checks the evidence again once the event arrives.
- 04 / Customer Success
Applies the health rule
Scores the account only once the events its health rule reads are arriving.
Connect the sources your health rule reads.
Skene checks what the rule depends on.
Bring the account rule and connect the sources it needs. Skene maps the required events and fields, then checks each one, such as plan_tier and support_ticket_opened.
Customer Success owns the decision.
Keep account segments, thresholds and interventions in your existing workflow. Tracking that exists in the code does not show whether the account was active in the last 30 days.
Check the events behind one account health rule.
Skene lists the events and fields the rule reads and checks each one. Your first experiment is free, with no card.
Measure your first experiment free