What is recorded

The script records most things by itself. You add code only for commerce events in manual mode, custom events, and linking sessions to customers.

Recorded automatically

Event	What it records
Page views	Every page load and client-side navigation, with time on page and scroll depth.
Clicks	The element clicked and up to 50 characters of its text.
Rage clicks	3 or more clicks in 700 ms on one spot, with no change on the page.
Dead clicks	A click on something clickable that changes nothing for 1.5 seconds.
JavaScript errors	Uncaught errors, unhandled promise rejections and console.error, with message and stack.
Network errors	Failed fetch/XHR requests and responses with status 400 or higher, on any host.
Network requests	Successful requests to your shop’s own host and subdomains. See URLs, requests and cookies.
Failed resources	Scripts, stylesheets, images and web fonts that did not load.
Form errors	Fields marked invalid: name and type, never the value.
Broken text	On cart and checkout pages: counts of broken characters (�, Å‚, Ä……), never the text.
Web vitals	LCP, INP, CLS, FCP and TTFB.
Products	Products seen on the page, from JSON-LD Product data (or OpenGraph).
Deploys	Your front-end version.
Session replay	If replays are on and the visitor allowed them. See Masking and replays.

Automated browsers (Playwright, Puppeteer, Selenium, Cypress, headless browsers) and known crawlers are treated as bots and left out.

Commerce events

The funnel (product → cart → checkout → payment → order) is built from commerce events. They come from automatic detection or from your own calls, never both. See Commerce: auto or manual.

Events you add

• Custom events with qm("track", name, props). See Custom events and customers.
• Page types with qm("page", { type }), when the URL does not say what a page is. See Page types.
• Customers with qm("identify", customerId). Only a hash of the id is sent.