Skip to main content

​
What it is

revenue_matched_rate is the share of your recurring revenue that comes from customers whose records are fully matched across your tools. The aim is 100%. It is the headline figure of the Customer matching module. A customer is Matched when it is found in every tool it belongs in, linked to its parent company if it has one, confirmed by a person on your team, and checked recently. Every other customer is To review. This figure tells you how much of your revenue already sits with customers you can count on being counted once, and correctly. It is published for your company as a whole, on the company and period object.
This value is not calculated yet. The rule below is Beacon’s, and it is fixed, but nothing works the figure out today. Every door returns not_computed for it, and the Customer matching page shows it as not yet calculated. Nothing is estimated in its place.

​
How it is calculated

Measured. Recurring revenue from billing for Matched customers, divided by all recurring revenue. It is a ratio from 0 to 1, shown as a percentage. Whether a customer is Matched comes from its match score, which has four parts with fixed weights: A customer is Matched when all four parts are complete, which puts its score at 100. A match Beacon joined on its own — the same email domain, for example — counts in your figures straight away, but it is not Matched until a person confirms it. So this figure can dip below 100% between reviews, as new customers arrive To review. Beacon never merges two records on its own, and never changes this rule itself.

​
Where it comes from

No read interface or MCP tool serves this value yet, and the value itself is not calculated yet. This table publishes its shape ahead of both.
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.

​
How fresh it is

Once calculated, it moves when a customer’s status changes or its revenue does. Which reading stands for a period is not yet declared; until it is, read the value with its own computed_at. Both timestamps travel with it: the moment the value describes, and the moment Beacon last worked it out.

​
Currency and rounding

It carries no currency of its own. It is a ratio of two totals that are both in your reporting currency.

​
What changes it

A person confirming a match, keeping two records apart, matching a customer by hand or undoing a match. A new customer arriving, which arrives To review. A subsidiary being linked to its parent. A customer going too long without a re-check. A customer’s recurring revenue changing.

​
What it is not

  • Not a count of customers. A few large customers to review can hold back more of this figure than many small ones.
  • Not the match score. The match score is worked out for each customer; this is the share of revenue whose customers score 100.
  • Not data_integrity_rate. That is the share of records passing Beacon’s daily checks.
  • Not something Beacon can raise on its own. Only a person’s confirmation makes a customer Matched.