More in Product analytics
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usHow it works
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.
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 an event until you accept it.
track() still work.Turn it on
- Open InsightsProject settingsCollection and enable Autocapture. The script lazy-loads the autocapture module on the next pageview; nothing to redeploy.
- Wait one night, or click Generate candidates now in the inbox. The first run needs a day of traffic to have something to cluster.
- Open InsightsDataEvent inbox. Four tabs: Pending, Accepted, Ignored and Event definitions. Cards on top count pending candidates, unplanned events, defined events and verified installs.
Review a candidate
Each pending row shows hits and distinct people over the last 7 days, when it was last seen, and whether the name came from a rule or from AI. Filter by high or low confidence, or by "not seen for 3 days" to clear stale ones. Expand a row to see the 7-day trend, first seen, the pages it occurred on and the actions people took just before and after.
Three actions:
| Action | What it does |
|---|---|
| Accept | Asks for an event name (starts with a letter), a label, a category and a description. Creates a match rule and backfills the last 90 days of autocapture so funnels have history on day one. A large backfill can take a few minutes. |
| Merge | Adds this interaction to an existing event's rules — for example, a second "Buy" button on a new page — and backfills only the increment. |
| Ignore | Moves it to Ignored. It stays there and can be accepted later; it does not come back as pending. |
Accepting, merging and ignoring require the Analyst role or above.
Unplanned events
The inbox also lists names your code already sends that have no definition — typically a track('checkout_v2') someone added in a hurry. They keep being stored, so no data is lost, but they clutter the event picker. Give them a definition, or set the definition to Blocked to stop storing them.
Use the events
Accepted events appear immediately in funnels, retention, paths and segments under InsightsBehavior. The usual first step is a funnel from landing page to the accepted sign-up click. The full product tour is on the Insights page.