> ## 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.

# Signals noticed

> How many signals Beacon noticed for your customers in a period, warning signs and good signs together. A headline figure of the Signals module.

## What it is

`signals_noticed` is how many signals Beacon noticed for your customers in the period: a payment that slipped, a customer that cut its plan, a deal that went quiet, a customer that grew. Warning signs and good signs are counted together. It is published beside [signal coverage](/definitions/signal-coverage-rate) as a headline figure of the [Signals module](/modules/signals).

It is published for your company as a whole, on the [company and period object](/data-model/company-period). The **Signals** page in Beacon shows the same count for the last 30 days, with how many customers the signals were on and how many were warning signs.

## How it is calculated

Measured. The number of signals Beacon recorded with a date inside the period. Each signal is counted once, on the date of the event it describes, whatever its direction.

Whether something counts as a signal is decided by the signal list: each signal has a fixed rule and, where it has one, a fixed cut-off — for example, how far usage has to drop. The cut-offs are set by your team's owner of the list and are never changed by Beacon on its own. That is why this figure is measured: the same records always give the same count.

**Signals fade, but not here.** When Beacon weighs what a signal means, an older signal counts for less. This figure ignores that: a signal noticed in the period is counted in full, however long ago in the period it happened.

**Whether a signal held back counts is not yet declared.** Beacon holds a signal back when the data behind it is not reliable enough. Whether such a signal is included in this count, or reported beside it, is still to be decided, and this article will say when it is.

## Where it comes from

| Source | What it supplies | Required |
| - | - | - |
| Your billing system | Revenue, payment and subscription signals | One of these |
| Your CRM | Deal and activity signals | One of these |
| Your accounting system, product usage tool and website analytics | More signals, as each is connected and read | Adds signals |

Today Beacon reads a first set of billing and CRM signals. The rest switch on as each is built; the **Signals** page shows which are on.

| 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 |

<Note>
  No read interface or MCP tool serves this value yet. The signals themselves can already be read one by one; this count over a period is not served yet. This table publishes its shape ahead of the doors.
</Note>

**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

It grows as Beacon notices new signals, after each read of your tools. **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. It is a whole number.

## What changes it

Something happening to one of your customers that a switched-on signal looks for. A new signal being switched on, or a new tool being connected — either can raise the count without anything changing in your business, so compare months with the same signals switched on.

## What it is not

* **Not good or bad on its own.** A rising count can mean more customers are growing, or more are slipping. The Signals page splits warning signs from good signs.
* **Not a share.** It grows with your number of customers. For how much of your customer base Beacon can see, read [signal coverage](/definitions/signal-coverage-rate).
* **Not a risk score.** Beacon publishes no overall risk rating from signals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.