Skip to main content

​
What it is

segment_account_count is how many active accounts a segment holds. It is published for a reason that has little to do with counting. It is the denominator every other segment figure is read against. A health score of 78 across 900 accounts and a health score of 78 across 11 are not the same claim, and without the count on the page there is nothing to tell them apart. It also makes a floor visible that is otherwise invisible. A segment must hold at least 10 active accounts, or at least 5% of your recurring revenue, to stand as a segment at all. Below that it is merged into the segment nearest to it, or kept as a small segment without a full health score. A segment sitting at 11 accounts is one departure away from that line, and the count is the only value that shows it.

​
How it is calculated

Measured. It is a count of the accounts assigned to the segment at the point the count is taken. Every account is assigned to exactly one segment, so segments do not overlap and no account is counted twice. Your set holds between 3 and 12 segments, so the counts are always spread across a small number of groups. Two related floors are worth holding together, because they answer different questions: A segment can clear the first and not the second. It exists, it is named, and results cut on it are still reported as an estimate across segments.

​
Where it comes from

Membership comes from the grouping described in segment. The accounts themselves come from billing and your CRM, after duplicate records have been resolved into one account. That resolution step matters more here than anywhere else in the segment figures. Two records for the same company count as two accounts until they are recognised as one, and an unresolved duplicate inflates a count without adding a customer.
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

Recounted each recalculation cycle, over the membership in force at that cycle. An account crossing a segment boundary changes two counts in the same cycle — one segment loses it, another gains it. Where more than 5% of a segment’s accounts move within 30 days, that movement is raised for review rather than absorbed quietly, because a count falling that fast usually means the grouping has shifted underneath rather than that customers have left.

​
Currency and rounding

Neither applies. A count is a whole number of accounts and carries no currency. Currency appears only in the alternative half of the population floor: the 5% test is measured on recurring revenue, which is read in your single reporting currency.

​
What changes it

An account joining or leaving the segment. A customer churning, or a new customer being placed. A duplicate being resolved, which can lower a count without anyone leaving. An approved merge, split or rename, which re-cuts the whole set at once. A new source being connected, which can deepen the grouping and move accounts between segments.

​
What it is not

  • Not a customer count for your business. It counts accounts inside one segment, as Beacon resolves them.
  • Not a count of contracts or subscriptions. One account can hold several of either.
  • Not a sample. It is the whole population of the segment, which is why it can be used as a denominator at all.
  • Not a measure of size in revenue terms. A segment of 40 large accounts can be worth more than one of 400 small ones; read it beside segment recurring revenue.