> ## 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 logo retention > The share of a segment's accounts still paying at each month of their life — a count of accounts rather than revenue, a ratio, and a curve rather than one number. ## What it is `segment_logo_retention` is the share of a segment's accounts that are still paying you at a given month of their life. It is a **count of accounts, not an amount of revenue** — every account counts once, whatever it pays. It is a **ratio, not a percentage**: 0.87 means 87% of the accounts that reached that month were still customers in it. At month 1 it is always 1.0. **It is not one number for a segment.** There is a value for every month of an account's life, from 1 to 36, and the line shows when a segment's customers tend to leave — early, at the first renewal, or slowly over years. It is read beside [segment net revenue retention](/definitions/segment-net-revenue-retention), and neither is complete alone. A segment can keep most of its accounts and still lose revenue, if the ones that stay pay less; or lose many small accounts and keep its revenue, if the large ones stay and grow. ## How it is calculated Measured. It comes out of Beacon's calculation layer, where the rules are fixed and written down, and the same billing always produces the same line. [Definitions](/definitions/overview) sets out what the three method words mean. ```text theme={null} segment_logo_retention at month m = accounts in the segment paying anything in month m / accounts in the segment that have reached month m ``` Accounts are lined up by their own first paying month, so month 1 is each account's first month wherever it fell in your history. An account counts at month m only once it has reached month m, and only closed months are read — the current month is left out until it ends. An account is still paying in a month if its recurring revenue that month is above zero. An account that left and came back counts as paying again from the month it returns. An account in no confirmed segment is not counted, and an account counts in its current confirmed segment. ## Where it comes from Billing, through your confirmed segments. Billing decides who is still paying, so it is the required connection; without at least one confirmed segment there is no line to draw. It belongs to the Segments module and is drawn on the [Segment revenue paths](/modules/segment-revenue-paths) page. Identity resolution decides what counts as one account. Where two records for the same business are not matched to each other, one of them ending reads as an account that left even though the business is still yours. | 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. **Why a count of accounts sits behind an opt-in.** There is no money in the arithmetic, but whether an account is still paying is decided by its revenue, so the figure carries the character of the revenue behind it. Every value about a segment sits behind an opt-in on every door. **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 Worked out every night, after your billing loads, over every closed month. A point can move after it is first drawn: as younger accounts reach a month, that month is struck again over a larger group, and an account moving to another segment takes its history with it. ## Currency and rounding No currency applies — it is a ratio of two counts. **No rounding rule is set for this value.** Today Beacon holds it to three decimal places — 0.875 — and whether that stays is not yet settled. A screen may show 87%; compare two points at the precision you received them. ## What changes it Accounts in the segment stopping paying, or coming back. Accounts reaching a new month of their life, which adds them to that month's point. Your segment approver changing which segments are confirmed. A resolved identity, which can merge two records that would otherwise read as one account leaving and another starting. An account paying less does not change it, however far it reduces. That shows in [segment net revenue retention](/definitions/segment-net-revenue-retention). ## What it is not * **Not a percentage.** 0.87, never 87. * **Not one number for the segment.** It is a value per month of an account's life. * Not [`logo_churn`](/definitions/logo-churn). That is the share of your whole customer base that left during a calendar period; this is the share of a segment's accounts still paying at a given age. * Not one minus the logo churn by year shown on the Segment revenue paths page. That chart counts accounts lost during each year of life against those still paying at that year's start; this counts against every account that reached the month. * Not a measure of revenue. Read [segment net revenue retention](/definitions/segment-net-revenue-retention) for that. * Not a forecast. Every point is billing history. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.