​
Overview

Userpilot can automatically capture events using the raw events auto-capturing feature, which captures events like Clicks, Text Inputs, and Form Submissions. This eliminates the need for manually adding trackable events, it starts collecting data (historical data) from the moment Userpilot is installed and auto-capture enabled, as the data is reflected in Userpilot immediately (real-time data). Auto-capture can be used in advanced segmentation, content triggering, and analytics (reporting), enabling stakeholders to make data-driven decisions.

​
Use Cases

  • Identify where your users are spending their time on your product
  • Get an intuitive view of your feature usage
  • Trigger content based on user behavior
  • Track users’ activity and understand what features they are interacting with
  • Defining a goal using raw events to measure the impact of your in-flows on user behavior

​
Raw Events Auto-Capture Enabling/Excluding

Under Configure - Settings, raw events auto-capturing can be enabled/disabled. This has to be enabled for Userpilot to collect users’ interactions (clicks, text input, form submissions). Excluding certain elements, domains, and locations can also be added under the exclude fields not to be auto-captured by Userpilot.

​
Types of interactions captured

  • Click: Any clicks on a button, link, or element (meaningful clicks/actions). In other words, clicking buttons with underlying mutations, links, or elements, each with a descriptive title.
  • Text Input: Typing a character or more into a text field, with each interaction tied to the field’s placeholder or input name. The description may include the placeholder text or the input name, depending on the field.
  • Form Submission: The user submits a form, typically via a button or submit input which triggers the underlying action or mutation to process the data entered in the form.

​
Labeling Raw Events

This is only available for Growth & Enterprise plans
Turning a Raw Event into a Labeled Event can be done by clicking “Label Event” or “Visaully label” next to the captured Raw Event. Some of the settings will be filled by the way the event was captured, but when labeling the event, it can be customized to your needs. Visually labeling the event gives the option to show the captured event in your web app for further perception. After the event has been labeled, it will appear under Overview with the rest of the events (tracked events, custom events). It can be used for segmentation, content triggering, and creating analytical reports.
Historical data that’s collected for Raw Events before labeling can be seen/used in Event Overview and Analytics (report creation). While creating Segments and Content Triggering would only consider data that was collected after Labeling the event.
Changing the configuration/targeting settings of a Labeled Event affects the historical data collected as well.

​
Supported CSS Selectors for Autocapture Raw Events

Examples: div, span, button, a, form, font, path, svg, input, etc…

​
FAQs