Skip to content
Docs
Browse Data Capture

Turn capture features on

What each capture card on a property does, and which are on from the start.

Each property has a card for every capture feature. Turning a feature on or off reaches the property's tag within a few minutes. Only admins can change how tracking is configured.

CardWhat it capturesStarts
Page signalsWhat kind of page each page is: the platform's page type, the template, the schema.org type, and counts of products, prices and fieldsOn
ClicksEach click on a link, button or picker, and each form sent without oneOff
ScrollingHow far down each page visitors got, and swipes on carousels and galleriesOff
FrictionPage speed, JavaScript errors, and rage, dead and error clicksOff
Data layerWhat the site keeps in its tag manager's data layerOff
Shopify CheckoutCarts, checkouts and orders from a Shopify storeOff

Page views are always captured.

Page signals

Page signals tell a product page from a cart on the Page types page. Only names from a fixed list and counts leave the page: no text, nothing typed into it and no value. With page signals off, page type rules can read only the page's path and data layer.

Clicks

Clicks are read in the Clicks explore, and the Click types page says what each click did. A form's submit sends what its fields held, and a search sends its term, but never a password, a card's security code, a one-time code, a PIN or an anti-forgery token. See Privacy and governance for what is kept.

Scrolling

Scroll depth is read in the Page views explore, and swipes in the Swipes explore. A scroll depth is only numbers: how far down the page a visitor got, in pixels and as a share of its height.

Friction

Friction adds about 10 KB, gzipped, to the tag every visitor downloads. See Struggle signals.

Data layer

Which data layers and analytics tools are read is set once for the whole organisation, on the Data layer page. The property's card only decides whether that property's pages are read. See Existing tags and data layers.

Delivery

The Delivery card sets how the tag sends events. Automatic sends each event at once, and, while the data layer is read, waits just past the page's snapshot so a page view and its data layer arrive together. A fixed window, from 1 to 5 seconds, sends fewer requests, a few seconds later. Either way, what the tag holds is sent as the page closes.

URL data

The URL data card lists the query parameters kept on page URLs, and lets you keep more, or keep the fragment after #. See Privacy and governance.