Signals
Some visitors do not bounce and do not convert. They get stuck. They click a button that does nothing, hit a script error, copy a code they cannot find again, or give up halfway through a form. Signals is the panel that surfaces those moments, ranked so the biggest source of friction sits at the top.
What Signals is
Signals is an aggregated breakdown, the same shape as the Goals view. Instead of a long list of individual sessions, it gives you one row per signal category, ranked by how often it happened. Each row shows two numbers: how many visitors triggered the signal and how many events it produced in total.
Click the caret on a row to expand it into its sub-items: the exact element selectors for rage and dead clicks, the copied strings for copied text, the script:line for script errors, and the form selectors for form abandons. Click any row to cross-filter the whole dashboard to the visitors behind that signal, so every panel, the map, the sources, and the KPIs reshape around them.
The six signals
Six signals feed the breakdown. Each one captures a different kind of friction, and each has its own detail page.
Three or more clicks on the same small spot within a second. The universal sign that something looks like it should work and does not. Sub-items are the element selectors that got hammered.
A click on something that looks interactive but does nothing. Working links and form fields are never flagged. Sub-items are the unresponsive element selectors.
A visitor selected and copied text from your page. Clickport keeps the first 200 characters, cookieless. Sub-items are the copied strings, so you see which codes and contact details people grab.
A JavaScript error fired during a real visit. Clickport stores the script filename and line only, never the error message. Sub-items are script:line pairs.
A visitor engaged a form and left without submitting. Clickport stores the form selector only, never field values or keystrokes. Sub-items are the abandoned form selectors.
A visitor printed or saved a page as PDF. A page-level count of reference intent, with no page content stored. This row is flat, with no sub-items.
How to read it
Two columns drive the breakdown.
- Visitors is how many distinct people triggered the signal. One person who rage clicks the same button five times counts as one visitor.
- Events is the total number of times the signal fired across everyone. The gap between the two columns tells you whether friction is widespread or concentrated in a few stuck visitors.
The table is ranked by frequency, so the biggest source of friction sits at the top. Expand a row with the caret to see its sub-items broken out the same way, with their own visitor and event counts. The Prints row is flat, because there is nothing to break it down by.
Click any row, or any sub-item, to cross-filter the whole dashboard to the visitors behind it. From there you can read where they came from, what they did before, and where they dropped off, using the rest of your panels as the lens. You can also add a signal filter from the filter editor and combine it with any other dimension; see Filters.
Inside an individual session, rage, dead, and copy signals still appear in the timeline next to pageviews, scrolls, and clicks, and on the session page lines as small badges: a red R for rage, an amber D for dead, and a purple C for copy. So you can read the whole visit around the moment a visitor got stuck.
Privacy
Signals is built to give you the insight of session replay without recording anyone. It is privacy-first by design.
- Cookieless. No cookies, no fingerprinting, no cross-session identity.
- No recording. No screen capture, no mouse paths, no keystrokes, no click coordinates.
- Thin by design. Each signal keeps only what it needs: a short element selector for rage and dead clicks, the first 200 characters for copied text, the script filename and line for script errors (never the error message), and the form selector for form abandons (never field values).
- No personal data. Selectors that look like they could carry personal data are dropped, and form fields never contribute their contents.
Where it lives
Signals is the Signals sub-tab of the Sessions panel. The other sub-tabs, All, Live, Converted, and Bounced, list individual sessions you can open and read. Signals is the one that aggregates: it rolls those same visits up into the ranked breakdown above, so you see the friction across your whole site at a glance instead of session by session.
Rage and dead clicks started life as frustration signals. Signals is the wider home for them, alongside copied text, script errors, form abandons, and prints. For how friction connects to the rest of your data, see Engagement.