Click autocapture

Every click captured automatically with the element it landed on: the Clicks view, dead-click detection, journey timelines and privacy rules.

With autocapture on, the snippet records every click on the page along with the element it landed on. No event code, no wiring: the moment the snippet is installed, the Clicks tab shows which buttons, links and controls your visitors actually use. Autocaptured clicks are never billed as events.

What gets recorded

Each click is described structurally, never personally:

Selector: a compact tag#id.class description of the control, e.g. button.subscribe. A tap on an icon inside a button is attributed to the button, not the icon.
Label: the control's visible text (a button caption, a link label), capped at 60 characters. For form fields the label falls back to aria-label, placeholder or field name; the value a visitor typed is never read.
Link target: for links, the destination as origin + path with the query string stripped.
Dead clicks: a click on nothing interactive is flagged. A pile of dead clicks on one element usually means something looks clickable but isn't.

Clicks on the page background record only the selector, so a stray click on a paragraph never captures page prose. Clicks also appear in each visitor's journey timeline, between the pageviews and custom events, so you can watch a session's clicks in order.

Where clicks show up

Overview, Interactions card: your custom events beside the autocaptured categories - Outbound (destinations of outbound-link clicks, with favicons) and Buttons (every non-link control, by its visible label). Clicking a row filters the dashboard to the sessions that clicked it.
Clicks tab: every clicked element in the period, most clicked first, with visitors, dead-click flags and the page it was clicked on. Searchable and sortable.
Journeys: each journey card counts its clicks, and the expanded timeline shows each one in place.
Stats API: GET /api/v1/clicks returns the same grouped data programmatically (see Stats API).

Turning it off

Autocapture is on by default. To disable it, add data-autocapture="false" to the snippet:

<script defer src="https://app.numative.com/numative.js" data-site="YOUR_ID" data-autocapture="false"></script>

Autocaptured clicks are stored as reserved __click events. They are excluded from your billed event count, from the Events card, and from custom property breakdowns, so nothing about your existing reports or bill changes when autocapture is on. Bot and automated traffic is excluded as everywhere else.