Features & data collection

The Features tab holds the top-level toggles. Turning one off stops the collection entirely — the SDK does not capture the data, so nothing is stored and nothing appears in the dashboard.

Toggles

• Error Logging — capture JavaScript errors from visitors' browsers. Feeds Error logs.
• Attack Detection — flag suspicious request patterns. Feeds Detected attacks.
• Rage Click Detection — record bursts of frustrated repeated clicking.
• Dead Click Detection — record clicks on elements that do nothing.
• Rage Click Feedback Prompt — when a rage click is detected, ask the visitor what went wrong. This is the one toggle here that is visible to visitors, so treat it as a product decision rather than a data one.
• Session Recording — the master switch for session replay. Detailed settings live on its own tab.

Data Layer

Separate from the toggles above, Read window.dataLayer lets the SDK mirror an existing Google Tag Manager data layer: a push carrying an event key becomes a tracked event, and a push without one becomes visitor context. Google Tag Manager keeps working unchanged.

This is the one toggle here that can double-count. If your site already calls Spectry.track() for the same actions it pushes to the data layer, turning this on records both. Pick one source per action.

Turning something off is not retroactive

Disabling a feature stops new collection. Data already captured stays until it ages out of retention or you delete the site.

Consent still applies on top

A feature being enabled here is necessary but not sufficient — the visitor must also have granted the relevant consent category. If a feature is on and you still see no data, check consent before checking anything else.