>unstuck engine
>Engine
>SignalsForty signal types, one pipeline>Waterfall enrichmentMulti-provider, ranked by reply rate>AudiencesSaved filters that update themselves
>Plays
>PLG AssistTurn free signups into enterprise pipeline>Inbound enrichmentEvery form fill, enriched and routed in seconds>ABMSurround the account, grade the buying committee
>Partners
>AgenciesPipeline as a service. With your name on top.>AdvocatesSix ways to advocate. Pick yours.
>Pricing
Book a Demo

> help

> Help index
  • 01What signals are and why they matter
  • 02Signal categories — 1st-party, 2nd-party, zero-party
  • 03The 31 signal types — a tour
  • 04Configuring autoqualify on a signal
  • 05Reading the signals table — column by column
  • 06Signal detail view — drilling in
Contents

Help / 05 · Signals

> Reading the signals table — column by column

The Signals page is a column-heavy table because it has to answer every question about your signal portfolio in one view — status, capture rate, qualification rate, downstream outcomes, credit consumption. This guide reads it left to right.

3 min read·Never reviewed

TL;DR: Open Signals. The table has identity columns on the left, state in the middle, performance metrics in the middle-right, outcomes on the right. Hide any column you don't use via Columns in the toolbar.

Identity cluster

  • Select — checkbox for bulk operations
  • Signal — signal name and icon. Clicking opens the signal detail view.
  • Status — current run state, color-coded
  • Autoqualify — toggle (see Configuring autoqualify)

Status states

  • 🟢 Running — signal is live and capturing
  • 🟢 Ready — configured and ready, but hasn't captured yet (new signal or no matches)
  • 🟡 Needs source — the signal type requires a source (LinkedIn account, webhook, CRM connection) that isn't connected
  • 🟣 Draft — not yet running; configuration in progress
  • ⚫ Paused — manually paused; preserves config, stops capture

State cluster

  • Profiles found — total records this signal has surfaced (lifetime, all-time)
  • L30D — sparkline showing the last 30 days of captures
  • Qualified — count of captures that ALSO matched an ICP / Persona, with the qualification rate (e.g. 842 / 45.0%). The headline metric — high qualification rate means the signal is well-aligned with your ICP; low means the signal is too broad or your ICP is too narrow

Performance cluster

  • Enriched — count and rate of qualified records that have at least one contact channel enriched (work email, personal email, phone, or LinkedIn). 758 / 90.0% means 758 of the 842 qualified records have at least one contactable channel
  • Synced — count and rate of qualified records that landed in at least one downstream destination

Outcomes cluster

The right side of the table tracks what happened to records the signal qualified, downstream. These columns reflect the value of the signal — if a signal qualifies thousands of records but none of them reply or sign up, the signal is noise.

  • Replied — count of qualified records who replied to outbound (any sequence, any channel)
  • Meetings booked — count of qualified records who booked a meeting
  • Signed up — count who signed up for a trial / product
  • Purchase — count who completed a paid conversion
  • LTV — aggregate lifetime value attributed to records this signal qualified
  • Credits used — credits consumed by this signal in the current billing window
  • Last run — timestamp of the most recent capture

Operations cluster

Far right. Hidden by default; surface via Columns.

  • Cost per profile — credits per captured record
  • Cost per qualified — credits per qualified record (cost-per-profile ÷ qualification rate)
  • Avg engagement at signal — engagement score average at the moment of capture

Filtering, grouping, sorting

The toolbar at the top:

  • Views — switch between saved views (Default, Custom)
  • Last 30 days — time range scope for L30D and outcome columns; click to change
  • Search — filter rows by signal name
  • Filter — multi-condition filter on any column
  • Group — group rows by Status, Cluster, or Source
  • Columns — show / hide columns
  • Autoqualify — bulk-toggle autoqualify across all rows

Two sanity checks

When auditing your signal portfolio:

  • Sort by Qualified rate descending. Signals at the bottom (low rate) are either misaligned with your ICP or sourcing noisy data. Pause or refine them.
  • Sort by Replied descending. Signals at the top are your highest-converting sources. Double their autoqualify confidence by tightening downstream filters; let them feed the highest-priority audiences.

Related

  • What signals are
  • Configuring autoqualify on a signal
  • Signal detail view — drilling in
  • What Insights tell you
Previous04Configuring autoqualify on a signalSignalsNext 06Signal detail view — drilling inSignals

On this page

  • Identity cluster
  • Status states
  • State cluster
  • Performance cluster
  • Outcomes cluster
  • Operations cluster
  • Filtering, grouping, sorting
  • Two sanity checks
  • Related

Share

> wave is here.

Schedule it.
>unstuck engine
PricingBlogContact
>unstuck engine

The B2B GTM engine. Signal-led targeting, ICP-fit pipeline.

Product

  • Pricing
  • Comparisons
  • Blog
  • Handbook
  • Help

Company

  • Contact

Legal

  • Terms
  • Privacy

© 2026 Unstuck Engine. All rights reserved.

> wave is here.

Schedule it.
>unstuck engine
PricingBlogContact
>unstuck engine

The B2B GTM engine. Signal-led targeting, ICP-fit pipeline.

Product

  • Pricing
  • Comparisons
  • Blog
  • Handbook
  • Help

Company

  • Contact

Legal

  • Terms
  • Privacy

© 2026 Unstuck Engine. All rights reserved.