The web page’s screenshot is generated by an ABTasty server that browses the URL and saves the page as an image.
The web page displayed in the Heatmap matches the Sample URL set during the Main information step of the campaign configuration process.
If the screenshot of your Heatmap does not match this sample URL, it may be due to one of the following reasons:
- The webpage is not reachable by a public server
- The webpage is relying on data coming from previous pages or on a session cookie
- The webpage is using a human verification system to block bots
- The webpage is behind a login wall
All these limitations are solved by using the “Retake screenshot” feature described here.
The web page is not reachable by a public server
If the URL is behind a proxy, or if it is an intranet web page, the AB Tasty server cannot screenshot the page.
The web page is relying on data coming from previous pages or on a session cookie
If the Heatmap is showing data coming from previous pages, such as a cart page showing items before checkout, or any page that comes after a form is submitted, our screenshot server cannot show it properly. This is due to the fact that the server browses the URL of the web page directly, and not the previous pages.
The web page is using a human verification system to block bots
If your Heatmap is showing a reCaptcha window (such as in the picture below), it means that our screenshot server has been blocked and cannot save the web page as an image.
The web page is behind a login wall
If the Heatmap is showing a login wall, it means that the web page requires authentication before being browsed.
In most cases, if the screenshot of your Heatmap is wrong, it is due to one of these reasons. If this isn’t the case, please contact your dedicated CSM.