More in Product analytics
- Autocapture and the AI event inbox
- Build a funnel that explains drop-off
- Identify users across web, app and mini-programs
- How do I review and accept events in the inbox?
- What are unplanned events, and how do I manage them?
- When should I use a funnel instead of a goal or path?
- How do I build a funnel?
- How do I read where a funnel drops off?
- What is identified mode, and should I turn it on?
- How do I call login to identify a user?
- How is one person merged across devices?
- How does identity work on apps and mini-programs?
- How do I track clicks on outbound links?
- How do I track file downloads?
- How do I track form submissions?
- How do I track custom events?
- How do I track button clicks?
- How do I create a heatmap?
- How do I track scroll depth?
- How do I track ecommerce purchases and revenue?
- How do I set up goals and track conversions?
- How do I query my data with SQL?
- How do I create a custom metric?
- How do I analyze accounts with groups?
- How do I connect AI agents with MCP?
- How do I ask the AI assistant about my data?
- How do I create user segments?
- How do I run an RFM analysis?
- How do I record and watch session replays?
- How do I analyze user paths?
- How do I build a retention report?
- How do I analyze how an event is distributed?
- How do I create a tracking plan?
- How do I view a user’s profile and activity?
- How do I read the lifecycle report (new, returning, resurrecting, dormant)?
- How do I compare attribution models for a conversion?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usShort answer
Autocapture records clickable elements — buttons, links and form submits — along with the page and the element’s selector, so an event exists before you name it. You do not need a developer to add track() calls first.
What it records
Without autocapture, an event exists only when a developer adds a track() call. With autocapture on, the script records clickable elements — buttons, links, form submits — along with the page and the element’s selector. Visible text is not captured by default, and password fields are always skipped.
Autocapture is included from the Pro plan. On Free the inbox page explains the plan does not include it; events from your own track() calls still work.
From clicks to candidates
Overnight, the inbox clusters the previous day’s interactions by element and page and suggests a name for each cluster — either from a rule (a button whose id is signup) or from a model (a link in the pricing table). Nothing becomes a real event until you accept it, which keeps your event list clean. Reviewing candidates is covered in how to review events.
Turn it on
Open InsightsProject settingsCollection and enable Autocapture. The script lazy-loads the module on the next pageview, so there is nothing to redeploy. The first run needs about a day of traffic before it has something to cluster.
Did this answer your question?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.