> For the complete documentation index, see [llms.txt](https://docs.sumble.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sumble.com/our-data/signals.md).

# Signals

The signal types Sumble detects, what each one means, and how a signal gets its priority.

A signal is a change at an organization that suggests a selling opportunity: a new technology in its job posts, a new project, a hiring surge, a key hire, or a tracked contact moving jobs. Sumble builds signals from the same job posts and people profiles as the rest of [its data](https://docs.sumble.com/our-data/our-data.md).

This page defines the signal types. To see and act on signals in the web app, see [Intent signals](https://docs.sumble.com/web-app/account-intelligence/intent-signals.md). To get them through the API, see [Signals API](https://docs.sumble.com/api/intelligence/signals.md). For delivery to Slack, your CRM or a webhook, see [Notifications](https://docs.sumble.com/system-setup-and-configuration/notifications.md).

## Signal types

### Technology adoption

An organization starts mentioning a technology in its job posts. It comes in three forms:

* **First mention by company.** The technology appears in the organization's job posts for the first time. The company is likely evaluating or adopting it.
* **First mention by team.** The technology appears in one team's job posts for the first time, even if other teams already use it. This catches a tool spreading inside a company.
* **Any mention.** Any new job post at the organization mentions the technology. Use it to keep watch on key accounts.

### Key technology projects

An organization posts jobs tied to a major technology initiative, such as a cloud migration or a generative AI project. A project usually means budget and an open evaluation. The full list of project types and what each covers is in the [filter reference](https://docs.sumble.com/our-data/filter-reference.md#project-types).

### Acceleration in job posts

Job posts for a technology or job function rise or fall by a statistically significant amount over a 12-month window. A surge in Kubernetes job posts suggests a company scaling its infrastructure. A drop in posts naming a competitor can matter as much as a spike in your own technology.

### New hires

A person with a given technology skill, or in a target job function, starts a new role at the organization. Sumble separates leadership hires (Manager and above, see [job levels](https://docs.sumble.com/our-data/filter-reference.md#job-levels)) from individual contributor hires. New leaders often bring the tools they used before.

### Growth in headcount

The number of people in a job function at the organization grows or shrinks. A signal needs both a meaningful percentage change and a meaningful absolute change, so small teams don't trigger on one hire.

### Competitor churn

Mentions of a competitor's technology fall while related migration projects appear. The company may be replacing that competitor.

### Own product churn

Mentions of your own product fall at an account. The customer may be reducing their use of it.

### Champion alerts

Your company gives Sumble a list of people from your CRM to track: champions, economic buyers, past users or anyone else you choose. Sumble alerts you when one of them changes companies. Someone who already knows your product, now at a new organization, is a warm lead.

Champion tracking is set up for Enterprise customers from the contacts in Salesforce or HubSpot. See [Salesforce](https://docs.sumble.com/system-setup-and-configuration/crm/salesforce-package.md) and [HubSpot](https://docs.sumble.com/system-setup-and-configuration/crm/hubspot.md#champion-tracking).

### Keyword tracking

Job posts mention a term that standard filters don't cover: a certification (SOC 2, HIPAA), a pain point (technical debt, scalability) or a methodology. Keywords are set up per customer.

## Priority

Every signal has a priority: high, medium or low. The priority comes from the signal configuration that produced it, so the same signal type can be high for one team and low for another. Web app filters, Slack delivery and webhooks all use it.

## Priority Signals

Priority Signals are short summaries Sumble writes of the most important signals for one person, drawn from the signals on their accounts. They appear in the web app, in Slack digests, through the [API](https://docs.sumble.com/api/intelligence/signals.md#search-priority-signals) and in [Salesforce](https://docs.sumble.com/system-setup-and-configuration/crm/salesforce-package.md#priority-signals).

## How often signals update

Signals are generated after Sumble's data refreshes, so they follow the schedule in [Data freshness](https://docs.sumble.com/our-data/our-data.md#data-freshness).
