Autocapture
Capture outbound clicks, downloads, form submissions, and media engagement without writing tracking code.
Autocapture records common interactions without you writing a track() call for each one. The web SDK
does the instrumentation and you turn types on and off from the dashboard.
Autocaptured interactions are ordinary events with canonical names, so everything that applies to your other events applies to them too: consent gating, attribution, filters, funnels, and queries.
Rolling out. Autocapture is being enabled account by account. The per-project toggle below takes effect only once it is on for your organization, so if captured events do not appear after you enable it, it is not yet live for your account. Contact us to turn it on.
Turning It On
Autocapture is off for every project by default. Go to Project Settings → Autocapture and switch on Enable autocapture, then choose the types you want.
Changes reach visitors without touching your installed snippet. The configuration rides along with the normal tracking response, and the SDK applies it on the next page load, so a toggle you flip now takes effect for returning visitors shortly after.
If no configuration is available for any reason, autocapture stays off. Pageview tracking is separate and is never affected.
What It Captures
Every type records metadata only. None of them record what a person types.
| Type | Events | What is recorded |
|---|---|---|
| Outbound links | Outbound Link | The destination URL and the link text |
| File downloads | File Downloaded | The URL, file name, and extension |
| Form submissions | Form Submitted | The form's id, name, and action, never field values |
| Video and audio | Media Played, Media Paused, Media Progress, Media Completed | Media type, source, title, percent, duration, and current time |
File downloads are detected from a link's download attribute or from a list of file extensions you can
edit per project, covering the usual documents, archives, and media formats.
Video and audio instruments native <video> and <audio> elements, recording play, pause, progress at
25, 50, and 75 percent, and completion. It records metadata only and never a recording. It is off by
default, because it suits some audiences and not others. Embedded third-party players such as YouTube,
Vimeo, and Wistia are not covered, since a cross-origin player does not allow this kind of listening.
Those need their own integration.
Autocapture does not do session replay, rich element capture, rage or dead clicks, or input-change capture.
Single-Page App Pageviews
Route changes in a single-page app are captured as pageviews by default, and this is a core SDK
behavior rather than an autocapture type. It is controlled by the SDK's own enableAutoPageviews
option, works whether or not autocapture is on, and has no dashboard toggle.
If your site is SPA-heavy, this is what stops in-app navigations from going uncounted.
Overriding Settings in the Snippet
The dashboard sets your defaults, and your snippet can override any individual setting for that one install. A snippet attribute can force a type on or off regardless of the dashboard.
The exception is the master switch. Naming a single type in the snippet sets that type's value but does
not by itself enable autocapture; the master toggle still has to be on, either in the dashboard or via
the data-autocapture attribute.
The mental model: the dashboard is your defaults, the snippet is a local override for one install, and the master switch decides whether any of it runs.
You can also tag any element with data-lgspt-event="Event Name" to emit a custom event on click, and
data-lgspt-prop-<key>="value" to attach metadata, without touching your JavaScript.
Privacy
No input values are recorded, ever. Form capture records the form's identifiers only. Password fields,
one-time codes, credit-card autofill, stored credentials, and anything you mark with
data-lgspt-sensitive are skipped entirely.
Because autocaptured events are ordinary events, they pass through the same consent gate. When analytics consent is denied, the event is dropped or anonymized according to your organization's setting, and Global Privacy Control and Do Not Sell signals are honored the same way. This is enforced on the server, so no snippet override can change what is allowed or stored.