On this page
  1. What it records and skips
  2. Sampling and block list
  3. The event inbox
  4. How long raw clicks are kept
  5. When to track by hand anyway
  6. Frustrated clicks

Autocapture needs Pro or above. The idea: record clicks first and decide afterwards which ones deserve analysis, instead of specifying every button up front and waiting for engineers to tag them one by one.

What it records and skips

With autocapture on, the script records clicks on clickable elements — buttons, links and elements with click handlers.

It skips:

  • Password fields.
  • Elements marked data-tc-ignore, including everything inside them.
  • Anything inside the live chat window.
  • Visible element text, by default. If you need text to tell buttons apart you can switch it on in settings; it only applies when the project's privacy level allows it.

To skip a single page, add data-autocapture="false" to that page's script tag.

Sampling and block list

  • Sampling — 100% by default. Busy sites can lower it; sampling is stable per device, so a person isn't in one day and out the next.
  • Selector block list — up to 20 CSS selectors whose elements are never recorded. Useful for frequent clicks with no analytical value, like carousel arrows.

The event inbox

Where: Product analytics › Data management › Event inbox.

Clicks don't become events directly. They are grouped into candidates once a day, or on demand. Each candidate shows the element, the pages it appears on and how often it was clicked. You can:

  • Accept it with a snake-case name such as click_book_demo. Accepting creates a rule and backfills the last 90 days, so you immediately see how often that button was clicked over the past three months.
  • Merge several buttons that mean the same thing in different places — the "Start free trial" in the header and the one in the footer — into one event.
  • Ignore what you don't need. Ignoring doesn't delete clicks already recorded.

Candidates are sorted by confidence; confidence affects order, not collection. Pro includes up to 200 AI-named candidates a day, VIP 1 500.

How long raw clicks are kept

Raw autocapture clicks are kept for less time than regular events: 3 months on Pro, 6 months on VIP 1, 12 months on VIP 2. Once accepted as an event, data follows the project's normal retention.

When to track by hand anyway

Autocapture is good at "how often was this button clicked". It is not good at:

  • Amounts and order numbers — a click doesn't know what was finally paid. Use server-side events.
  • Outcomes rather than clicks — someone can click "Create account" and fail on a captcha. Record "sign-up succeeded" as a custom event in the success callback.
  • Pages whose structure keeps changing — if a button's position and markup change with every redesign, rules may stop matching. A stable id or data-* attribute on key buttons helps a lot.

What works best is a mix: autocapture for the long tail of minor interactions, hand-tracked events for the dozen business events that must be exact.

Frustrated clicks

With autocapture on, three quick clicks in the same spot also record a frustrated click. They show up on the errors page and on heatmaps, and are good at finding elements that look clickable but don't respond.