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 downstream to the people a signal reached. These columns are how you tell a valuable signal from a noisy one.
6 of them carry a muted touch-attributed label under the header. Read that label before you read the number. When someone replies or converts, every signal that reached them in the 365 days before is credited — not only the last one. So 1 reply adds 1 to Replied on every signal that touched that person, and the column sums to more than the number of replies you actually received. The full model is in Replies and Conversions.
- Replied — replies attributed to this signal, on any channel
- Meetings booked — meetings attributed to this signal
- Signed up — product or trial signups attributed to this signal
- Custom conversions — conversions you named yourself on a Conversions webhook (Upgrade, Trial started, Renewal), attributed to this signal
- Purchase — paid conversions attributed to this signal
- LTV — purchase value attributed to this signal, summed off the same events as Purchase
- 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
2 sanity checks
When auditing your signal portfolio:
- Sort by
Qualifiedrate descending. Signals at the bottom (low rate) are either misaligned with your ICP or sourcing noisy data. Pause or refine them. - Sort by
Replieddescending. This ranks your signals against each other, which is what the column is for. It is not a conversion rate. A signal that reaches a lot of people appears in a lot of journeys, so volume lifts it too — read it next to theQualifiedrate before you decide a signal is earning its place.