> ## Documentation Index > Fetch the complete documentation index at: https://docs.beaconrevenue.io/llms.txt > Use this file to discover all available pages before exploring further. # Segment health score > A 0-100 measure of how one segment is doing as a commercial group, its six weighted dimensions, and why carrying no money no longer opens a door to it. ## What it is `segment_health_score` is a 0-100 measure of how one segment is doing as a commercial group, where a higher number means a healthier segment. It describes the group, not the accounts in it. A segment can score well while accounts inside it are struggling, and badly while most of its accounts look fine — because it also reads how efficiently the segment acquires customers and how much of the intelligence behind it is there at all. The score carries no money. It is a number between 0 and 100 with no currency and no amount inside it, even though one of the six dimensions behind it reads revenue. That does not make it open by default. Every door takes an opt-in, and *Where it comes from* says where that choice is made. ## How it is calculated Measured. Six dimensions are each scored 0-100 and combined at fixed weights. | Dimension | Weight | What it reads | | - | - | - | | Revenue trajectory | 0.25 | Which way the segment's recurring revenue is moving | | Retention stability | 0.25 | Retention across the segment, and how steady it is | | Acquisition efficiency | 0.18 | What it costs to win an account in this segment against what that account returns | | Customer quality | 0.17 | How closely the segment's accounts match the customers you do best with | | Intelligence reliability | 0.10 | How complete and confident the data behind the segment is | | Lifecycle position | 0.05 | Where the segment's accounts sit across their lifecycle | The six weights sum to 1.00. A segment scoring 72, 80, 64, 70, 66 and 58 across the six, in the order above, scores 70.9. The weights are fixed and the arithmetic is fixed, so the same six dimension scores always produce the same result. What you cannot do is re-run it from your own records: each dimension is itself an average of what the active parts of Beacon report for that segment, and those readings are Beacon's rather than raw data you hold. The fewer parts are active, the wider the confidence band published beside the score. The band is part of the answer: a score of 70 with a narrow band and a score of 70 with a wide one are not the same claim. The six weights are fixed and are the same for every company. Changing one is a decision made by whoever owns segmentation in your business, and it is never applied automatically. ## Where it comes from Each dimension is supplied by a different part of Beacon, and each depends on the sources behind it. | Dimension | Depends on | | - | - | | Revenue trajectory | Billing — recurring revenue over time for the segment's accounts | | Retention stability | Billing — retention across the segment | | Acquisition efficiency | Marketing and sales cost against the value the segment returns | | Customer quality | Fit scoring, which reads firmographic and engagement data | | Intelligence reliability | The data-confidence measure behind each account in the segment | | Lifecycle position | The stage each account has reached after the sale | Where a source is not connected, the dimension that depends on it does not contribute and the confidence band widens. Nothing is estimated in its place, and no dimension is silently reweighted to cover the gap. | Where it is available | | | - | - | | Read interface | Yes, with an opt-in | | MCP | Yes, with an opt-in | | Events | Yes, with an opt-in | | CRM property | Yes, with an opt-in | No read interface or MCP tool serves this value yet — the table above publishes the shape ahead of the doors. **Where the choice is made.** This value is not open by default on any door. The choice happens when a reader grant that reaches it is issued or widened, when you subscribe to events, or when you turn the CRM property on. Whoever makes it is shown who becomes able to see the value, and their yes is recorded — holding a grant is no longer enough on its own. ## How fresh it is The score belongs to a recalculation cycle rather than to a moment: one score per segment per cycle, worked out after the intelligence feeding it has updated. The cycle is a daily consolidation, and a movement of five points or more between cycles is treated as material. Both timestamps travel with it — the moment the score describes, and the moment it was last worked out. For a value composed from this many inputs they are rarely the same. ## Currency and rounding Neither applies to the score. It is a 0-100 number with no unit. Money appears only inside the dimensions. Revenue is converted into your single reporting currency before it is scored, so a segment billing in three currencies is not scored differently from one billing in your own. ## What changes it Movement in any of the six dimensions — retention firming or softening, revenue turning, acquisition getting cheaper or dearer, the quality of the accounts being won, the completeness of the data, the stages the segment's accounts sit in. Membership changes it too, and this is the one people are caught by: the score is worked out over the segment's members at the time of the cycle. When accounts move between segments, both scores move without anything changing at any account. Connecting a new source can move the score and narrows the band. An approved change to a weight, or an approved merge, split or rename, re-runs it. ## What it is not * Not [`health_score`](/definitions/health-score). That measures how strongly one account is progressing through its lifecycle. This measures a group, on different dimensions, for a different purpose. * Not an average of the health scores of the accounts in the segment. Four of the six dimensions read things no account-level score reads at all. * Not the six dimensions that form segments. [Segment](/definitions/segment) is built on six weighted dimensions and so is this score, and they are different sets with different weights — one decides which group an account belongs to, the other says how that group is doing. * Not a rank. A score of 70 is a level, not a position against your other segments. * Not a money figure. What the segment is worth is [segment recurring revenue](/definitions/segment-total-arr). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.