Click autocapture

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 section 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. Repeat clicks on the same element are capped per page: the reports show which elements get used, so the first few clicks carry all the signal and a rapid-fire burst on one button is not recorded hundreds of times.

• 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.

Form submissions

The snippet also records every form that actually submits, which is a different fact from a click on the submit button: the click happens whether or not the form validated. Numative reports the pair, so clicks without submissions makes client-side validation failure visible, and neither half shows it alone.

Field values are never read. A form is described by the same structural selector everything else uses, plus a name taken from its own name, id or aria-label, its action stripped to origin and path, and how many fields it has. Turn it off with data-forms="false". Full detail in Enhanced measurements.

Where it all shows up

• Overview, Interactions card: your custom events beside everything captured automatically. Forms (submissions, with the attempts behind them), Links (every link click, internal and external), Outbound (destinations off your site, with favicons), Affiliate (once you have named your affiliate paths), Buttons (every non-link control, by its visible label) and Dead clicks. Clicking a row filters the dashboard to the visits that clicked it.
• Clicks section: headline counts for clicks, visitors clicking and dead clicks, each against the previous period, then every clicked element in the window, most clicked first, with 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.
• Filters: links, outbound links, affiliate links, buttons, dead clicks and form submissions are all filter dimensions, so any of them can narrow the whole dashboard.
• 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>