Contentsquare can only collect data on pages where the Contentsquare tag has been installed. If a page isn't being tracked, check that the tag is present before troubleshooting further.
Troubleshooting checklist:
Clear your browser's cache and cookies. In many cases, the root cause can be related to the cache. Clear your browser's cache and cookies, then check whether the issue is resolved before moving forward.
Make sure the web page finishes loading before taking a snapshot in the Zoning analysis. Scroll all the way to the bottom of a page to confirm that loading is complete before taking your snapshot and saving it.
Check the chosen time period in the analysis context:
- Was the Contentsquare tag active at that time?
- Has the page changed between the date the zoning was created and the selected time period? For example: your page changed on January 8th. You created the zoning on January 19th. Choose a time period starting after January 8th for your analysis.
How do Zoning and Replays collect 'Static resources' to automatically recreate my site?
Read this article to learn more about how Contentsquare collects your site's Static resources using the CS Scrapers.
How do Zoning and Replays use 'Live assets' when static resources are unavailable?
Live assets use the live URLs of a page's resources (CSS, images, fonts) to render that page inside Contentsquare's Zoning analysis and Session replay features if the CS Scrapers are unable to download and store all of your static resources.
- In Zoning analysis, if static resources are not available, Contentsquare fetches content from your live site for you to analyze.
- In Session replay, if static resources are not available, you can temporarily select the 'Use live assets' option in the player to analyze data from your live site.
Why is my zoning/replay not displaying correctly?
Pages using the HTML <dialog> element may fail to load properly in Zoning or CS Live.
We’ve identified a technical limitation that prevents snapshots from displaying correctly where the <dialog> element is present. We’re actively exploring solutions and will update this page.
There are several reasons Contentsquare would be unable to download your site's static resources:
| Authentication | the resource is authenticated (usually with a cookie) |
| Geographic restriction | the resource is only available for some geographic locations (usually by country) |
| VPN | the resource is behind a private network and not available on the internet |
|
Special headers/cookies
|
the resource requires a specific header or cookie
|
|
IP ban
|
the gateway-proxy IP is banned by the target client-server
|
How to make zonings and replays work with your website
You may need to work with your Content Delivery Network (CDN) provider.
The following methods are available to configure your site to work with Contentsquare.
Use a custom static header
This is the recommended method for allowing Contentsquare's scraper to access your static resources.
A custom static header lets you configure your CDN or server to recognize and allow requests coming from Contentsquare. For full implementation instructions, see Using a custom static header in the Contentsquare technical documentation.
If you need help configuring this with your CDN provider, contact Contentsquare Support.
Whitelist Contentsquare IPs
It may be necessary to whitelist Contentsquare IPs. See the guide on IP Addresses and Domains to Whitelist.
Use a proxy
Contentsquare can help you bypass geographic restrictions using a proxy for a different location. A proxy has its own IP address and can operate in a specific region of the world.