QA Heatmap Analyticsのご愛顧ありがとうございます。 11月2日にVer0.9.0.2を公開しています。 * 動画再生機能の実装 * ダッシュボード、ヒートマップ管理画面のUIを調整 * ヒートマップ管理画面 タイトル下にページのスラッグを追加 * 不具合修正
I think the click heat map and click count map are misaligned.
If you resize your browser slightly, it will redraw the image and draw it in the correct position. The reason why all the heatmaps, link clicks, etc. are misaligned is because the delayed indication of ads and delayed loading of images causes the positions to be off from the initially calculated positions. Therefore, redrawing the various maps will fix the problem.
The range of clicks in the click count map is too large.
If there are no closing tags such as input or a tags in the HTML source code, the range of the click map cannot be determined and the range may become larger. Please check the source code.
The number of data is displayed, but the heatmap view is not displayed.
The heatmap bar may not be displayed if there are no closing tags such as /body in the HTML source code of the template you are using. Also, if allow_url_fopen is not turned on in your php.ini settings, you will not be able to display the heatmap.
I got a cron error.
Depending on the rental server, there may be restrictions on the nighttime cron operation. In such the case, it is recommended to reduce the number of pages to be measured, so that the cron can finish its work faster. If the error does not get resolved even if you reduce the number of measurement pages significantly, the problem may be caused by a problem with the server environment. If you would like to report a problem to the development team, please contact us and report the problem anonymously.
I got a curl: SSL connect error on license activation.
This error is displayed when the encrypted communication with the activation server fails. It occurs when your rental server uses a vulnerable older generation encrypted communication module. As a countermeasure, please send information about the curl: SSL connect error to your rental server company, and update the encrypted communication module on the server side, as this often solves the problem.
The number of data will be zero.
There are five major possible causes. The first is a problem right after installation. In this case, the data count will be zero because the aggregation process has not yet taken place. Try to access it again in 24 hours. The second is when a JavaScript error occurs; if a JavaScript error occurs, you may not be able to measure correctly and data may not accumulate. This is especially true for the jQuery version. For more information on how to check if an error is occurring, please refer to How to figure out the cause of JavaScript or jQuery not […]
The number of data is less than I expected.
QA Analytics uses JavaScript and 1st-party-Cookie to try to collect as much data as possible. However, it does not match all the numbers with Google Analytics, for example, because it uses a different method of data acquisition than other tools. However, if you feel that the numbers are obviously wrong, for example, the number of data is only half, please check the following. Check to see if the corresponding article has been updated recently.When you update, the data is stored in the new version, so it looks like the data has been reduced. See if the number is close to […]
I have activated it, but the QA Analytics menu do not appear on the admin screen.
QA Analytics cannot be enabled because you do not have write permission for the file. Please refer to following URL Please check if you are getting the above error. If you get this error, it is possible that the server does not have permission to write to the directory. To deal with this, please grant write permission to the wp-content directory by the web server, and change FS_METHOD to direct or ftpext in wp-config.php. For more information about FS_METHOD, refer to this article and other useful articles. After granting the permissions, re-enable it.
How to exclude your own visit
QA Analytics does not measure access by users who are logged in, regardless of their WordPress user permissions. Therefore, if you wish to exclude yourself from visiting your site, log in to your WordPress first.