> For the complete documentation index, see [llms.txt](https://docs.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icustomer.ai/audience/signals.md). # Signals The events that move scores and trigger decisions, and where they come from. A signal is an event that tells the system something changed about an account or a person, the raw material every score and decision is made from. ## What counts as a signal * **What they do on your surfaces**: site visits, pricing-page views, form fills, demo requests, email opens and replies. * **What changes at the company**: hiring for the problem you solve, new leadership, funding, adopting a tool you integrate with. * **What your systems say**: CRM stage changes, deal activity, product events where connected. ## Where signals come from First-party first: [the pixel](/integrations/events-and-pixels.md) and your connected tools carry the highest trust, because they are observed, not reported. Enrichment and intent sources add the outside view. When sources conflict, trust order decides; see [Context and memory](/concepts/context-and-memory.md). ## Two properties that matter * **Signals attach to identities, not sessions.** A signal is only useful once it belongs to a resolved person or account, which is why [identity](/audience/identity.md) and clean domains come first. An event that cannot resolve waits; it is not guessed onto someone. * **Signals age.** A pricing visit last week is not one from last quarter. Freshness is built into scoring through Recency, so the picture decays honestly instead of accumulating forever. ## What signals do They move [FIRE scores](/audience/fire-scoring.md), they trigger pulses when a moment needs a human, and they start plays whose conditions they meet. A strong single signal, a demo request, say, can flip an account Hot and set the loop in motion within the moment it happens. {% hint style="info" %} How fresh signals arrive follows your plan: daily-batched on Pro, live stream on Team and above. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.icustomer.ai/audience/signals.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.