PostHog Handbook Library / Customer Success

2,861 words. Estimated reading time: 13 min.

Customer health tracking

Auto TL;DR

At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

  1. Where to find it
  2. Account health dashboard
  3. The account health scores view
  4. Who gets scored
  5. The rule: people compared to agents
  6. Why the score is built this way
  7. Why two axes instead of one
  8. Why 61.5 / 38.5

We track customer health in Customer Analytics. Each paying or trialing account gets a health score out of 10, refreshed once every 24 hours. For how recently accounts with an assigned owner contacted us, see Automated relationship score. For the rating you set by hand on your own accounts, see CSM relationship.

We can't yet see historic trends of customer health, because the score is a materialized view that is rebuilt each day.

We purposefully don't include data volume increases or decreases in this score. Spike alerts capture these, and they need a different response from a health score trend (immediate action).

Where to find it

Each account in Customer Analytics has these properties:

| Property | What it tells you | | --- | --- | | Health score | Product health, 0–10. Refreshed daily. | | Health score updated | When the score was last calculated. A date older than about one day means the score is stale. | | MCP users (weekly) | The average number of people who used the PostHog MCP each week in the last 3 weeks. | | MCP share (%) | The share of the account's active people who use the MCP. | | Health dashboard | A link to the Account health dashboard, filtered to this account. |

Account health dashboard

The Account health dashboard is the overview and deep dive for one account. To open it:

  1. Open the account in Customer Analytics.
  2. Click the Health dashboard link in the account's properties.

The link sets the organization_id variable for you. You can also open the dashboard directly and type an organization ID into the variable at the top. Only paying or trialing accounts have a score, so only those accounts have a link.

The dashboard shows:

The account_health_scores view

The full breakdown per product is in the account_health_scores view in the PostHog Data Warehouse. You can also add it from the column selector in Customer Analytics.

The view has three main numbers per account, all out of 10:

| Column | What it tells you | | --- | --- | | engagement_health | Are the people who use PostHog at this account still using it? Trend-based, measured against the account's own history. | | stickiness | How embedded is PostHog in their stack? Absolute, not trend-based. | | health_score | The headline blend: 0.615 × engagement_health + 0.385 × stickiness. |

The view also has a per-product breakdown (e_*) and each product's share of the engagement score (contrib_*). It runs entirely on PostHog-native data: events, the billing usage report, and our own revenue tables.

Who gets scored

An account gets a score if one of these is true:

The score_status column tells you how to read the score:

The rule: people compared to agents

Calls from agent tokens (scouts, research, and sandbox runs) do not count as engagement. They count in stickiness through the scouts and scanners that the customer set up.

Why the score is built this way

Why two axes instead of one

Engagement and stickiness fail in different directions, and a single number hides that.

Engagement is a trend, measured against the account itself. A five-person startup with 3 weekly active users is not less healthy than a 500-person enterprise with 30. It's the trend that matters. A small account holding steady scores well, and a large account that's halved scores badly, which is the right way round for a CSM triaging a book.

Stickiness is an absolute measure of how hard PostHog is to remove. An account can have flat engagement and still be extremely safe, because they have destinations piping data out, warehouse syncs, and scouts running. Ripping that out is a major undertaking. Conversely, an account can be highly engaged and still easy to churn if all they do is look at dashboards.

Two accounts at 6.5 overall can be completely different problems. Always read the two components, not just the headline.

Why 61.5 / 38.5

The full health model weights product engagement at 0.40, stickiness at 0.25, and customer relationship at 0.35. Relationship is not in this score. It is a separate property, Relationship score (see Automated relationship score). This view only covers the two product axes, so those weights are renormalized to sum to 1: 0.40 / 0.65 = 0.615 and 0.25 / 0.65 = 0.385.

How stickiness is measured

Stickiness has two equal halves:

stickiness = 10 × (0.5 × breadth + 0.5 × depth)

breadth = min(engaged product weight / 19, 1)

depth = min(( pipelines × pipeline_retention
            + 3 × [mcp_users > 0] × (1 + min(mcp_users / 10, 1))
            + 2 × [scanners  > 0] × (1 + min(scanners / 5, 1))
            + 2 × [scouts    > 0] × (1 + min(scouts / 5, 1))
            + 1 × [evals     > 0] × (1 + min(evals / 5, 1)) ) / 24, 1)

pipelines = 3 × [destinations > 0]    × (1 + min(destinations / 5, 1))
          + 2 × [warehouse syncs > 0] × (1 + min(syncs / 10, 1))
          + 2 × [transformations > 1] × (1 + min((transformations − 1) / 5, 1))
          + 1 × [batch exports > 0]   × (1 + min(exports / 3, 1))

The view also shows the inputs as columns: active_destinations, active_transformations, active_batch_exports, active_warehouse_syncs, pipeline_retention, active_scanners, active_scouts, and active_evals.

How we measure engagement for each product

Two sources feed each product: UI events, and MCP tool calls attributed by category.

| Product | Weight | UI signal | MCP $mcp_tool_category | | --- | --- | --- | --- | | Product Analytics | 3 | insight viewed, viewed dashboard | Product analytics, Dashboards, Insights & analytics, Query wrappers, SQL, Data schema, Data catalog | | Session Replay | 2 | recording viewed | Session replays | | Feature Flags | 2 | feature flag created, feature flag updated, toolbar feature flag overridden | Feature flags | | Web Analytics | 2 | $pageview on the Web Analytics page | Web analytics, plus the query-web-stats, query-web-overview, and heatmaps-* tools | | Error Tracking | 2 | error_tracking_issue_viewed | Error tracking, Error tracking alerts | | AI Observability | 2 | llm analytics usage | AI observability, plus the query-llm-trace and query-llm-traces-list tools | | Experiments | 1 | experiment viewed | Experiments | | PostHog AI | 1 | max conversation turn completed, task_created from PostHog AI | – | | Surveys | 1 | survey viewed | Surveys | | Logs | 1 | logs query executed | Logs | | Inbox | 1 | Inbox viewed, Inbox report opened, Inbox report action, Scout fleet viewed, Scout config changed | Signals | | Replay Vision | 1 | scanner viewed or created, observation viewed, watch feed viewed | Replay vision |

Why some weights are set this way:

Inner workings

This section is a detailed drill into the mechanics of the score. You don't need it to use the score day to day. It records how we compute the score and why.

How engagement is calculated

For each account and each in-scope product, over an 84-day lookback:

  1. Count weekly active users. Distinct persons who fired that product's qualifying event, bucketed by week. UI events and MCP calls both count.
  2. Current level: mean WAU over the last 21 days.
  3. Baseline: median WAU over weeks older than 28 days. Median rather than mean, so a single spike week doesn't inflate the bar the account has to clear.
  1. Score the product:
   e_p = NULL                              if no baseline (never meaningfully active)
   e_p = 0                                 if there is a baseline but zero current activity
   e_p = min(current / baseline / 0.85, 1) otherwise
  1. Blend across products, weighted:
   engagement_health = Σ(weight × e_p) / Σ(weight)     over products where e_p is not NULL

contrib_* splits that blend back out per product. They sum to engagement_health, so you can see at a glance which product is dragging a score down.

Reading e_*: NULL and 0 mean very different things

An account showing e_session_replay = 0 deserves a conversation this week. One showing NULL deserves a demo at some point.

Why the 0.85 grace band

Engagement compares current activity to the account's own historical median, but real usage is noisy: holidays, sprint cycles, one person on leave. An account only needs to hold 85% of its own baseline to score a full 10. Below that, the score falls off proportionally. This stops the score flapping on ordinary week-to-week variance.

Automated relationship score

The Relationship score property is a score from 0 to 100 that we calculate each day. It measures how recently the customer contacted us. It does not measure how happy the customer is: a high score means that somebody talks to us, not that the conversation goes well.

Every account with an assigned CSM, TAM, or account executive (AE) in Customer Analytics gets a score. If an account has more than one, the owner is the CSM, then the TAM, then the AE.

Each account in Customer Analytics has these properties:

| Property | What it tells you | | --- | --- | | Relationship band | The band of the score (see below). Read this first. It shows Unknown when the account has no signal. | | Relationship score | The score, 0–100. |

Signals

| Signal | Weight | What counts | | --- | --- | --- | | Slack | 30 | Inbound messages in the customer's shared Slack channel, and support tickets that come from Slack. Messages from bots are not counted. | | Support tickets | 25 | Support tickets from the customer that do not come from Slack. | | Meetings | 25 | Gong calls linked to the account, and confirmed past meetings on the account in Customer Analytics. | | Email | 25 | Inbound email from the customer, captured from Gmail in Customer Analytics. Email from PostHog addresses and no-reply addresses is not counted. |

Each customer contact counts in one signal only. For example, a Slack message counts under Slack, and not again under support tickets.

How the score is calculated

Each signal gets a sub-score from 0 to 100:

sub_score = min(max(100 − days since last contact + volume bonus − penalty, 0), 100)

The relationship score is the weighted average of the signals that the account has. A missing signal does not lower the score. For example, an account with no Gong calls and no calendar meetings gets a score from the other three signals.

| Band | Score | | --- | --- | | Strong | 80 and above | | Healthy | 60 to 79 | | Cooling | 40 to 59 | | Cold | 20 to 39 | | Dormant | Below 20 | | Unknown | No signal |

Where to see the data

The Relationship score section of the Account health dashboard shows:

The full breakdown is in the csm_relationship_scores view in the PostHog Data Warehouse.

Limits

CSM relationship

The health score and the relationship score above are computed for you. CSM relationship is a rating you set by hand on your own accounts, in Customer analytics.

It records the relationship you personally have with the account. It does not measure how the account is doing from a usage/spend/metrics standpoint. A large, healthy, fully self-serve account can sit at the bottom of the scale, and that is a correct reading in a product-led book, "assigned to you" and "known to you" are different things.

| Rating | What it means | |--------|---------------| | 1 - No relationship | The account is yours on paper only. It is fully self-serve, and you have no two-way contact with anyone there. | | 2 - Introduced | Warmly introduced from another team member but no direct trust yet OR limited response to engagement attempts but no real relationship built | | 3 - Reactive | They contact you when they need something, and there is no contact between times. | | 4 - Working relationship | You have regular two-way contact with a named person who replies to you and takes meetings. | | 5 - Trusted advisor | You are multi-threaded in the account. They bring you problems early and include you in their plans. |

To set the rating, add the CSM relationship column to your account view, then click the cell.

How to use it

Each label starts with a digit, so the scale sorts in the accounts table and totals in HogQL and PostHog AI. Use toInt32OrNull(substring(value, 1, 1)) to get the number.

Canonical URL: https://posthog.com/handbook/customer-success/health-tracking

GitHub source: contents/handbook/customer-success/health-tracking.md

Content hash: 825a189232830e49

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: PrivateLink.