Contentsquare captures the majority of user sessions, however it may not be possible to capture 100% of all your site visitors.
A checklist to understand why not all traffic can possibly be captured
-
Sessions less than 30 seconds: By default, Contentsquare disregards sessions under 30 seconds. You can modify your site settings to include these shorter sessions. This can often explain differences between Contentsquare and other analytics data.
- Session targeting is in use: If you are targeting session capture based on specific events being triggered or URLs that are targeted, this will result in fewer sessions being collected.
- Content Security Policies: If your website has a Content Security Policy, ensure it allows Contentsquare to operate. Otherwise, your site may block Contentsquare and prevent data collection.
-
User settings: A user's browser and/or local network environment can preventing session capture. This can include:
- A user's browser or network environment preventing session capture, such as unsupported browsers, JavaScript/cookies disabled, Do Not Track enabled, or private/incognito mode blocking tracking.
- The visitor has disabled localStorage or sessionStorage, or uses plugins, extensions, or privacy tools that block the Contentsquare tag.
- Accessing your site from a network that restricts Contentsquare's servers, blocks WebSocket connections, or experiences connectivity issues can prevent session capture.