r3098

Just because mouseflow works, it doesn’t mean that there is no problem on the site side.
Perhaps if you log in to the site, you can get the cause of the problem.
In the unlikely event that Aurora Heatmap is the cause of the problem, we may be able to help you deal with it.
If you wish, please send me an email with the information.
[email protected]

In the page you presented, the minify process is done as shown in the previous guide.
I can’t say for sure that it is directly related to the heatmap rendering, but there is also a JavaScript error.
I think it may be caused by Autoptimize, so could you please try deactivating this plugin first?

Hello.
You mean there is a heatmap count and if you click on it, the window opens?
Does it have a gray overlay on it as you can see in the demo movie?
If not, then there is something wrong with the JavaScript running, such as h337.js, which is used to draw the heatmap.
You can get information about JS errors on the console of the validation panel.
As for cookies, you don’t need any special permissions unless you have blocked the standard WordPress cookies.

Caching plugins and the Minify process that compresses JS may interfere with normal operation in some cases.
Please refer to the following as well.
https://market.seous.info/en/aurora-heatmap#oc-1

Hello.
Users click where they gaze and where they are interested.
Heatmaps measure this and render it.
This is not limited to link elements.
I’ve looked at your site and it seems to be working fine.
Eighty clicks on the edge of a seemingly empty screen seems odd, but that is exactly what the user is doing.
Of course, there are some behaviors that don’t make sense, but as more data is collected, we should be able to see a trend.

First of all, Aurora Heatmap works fine with WordPress 5.7.
Aurora Heatmap only displays data when the page is accessed.
The data we collect is screened to ensure accuracy.
In addition, it does not retrieve administrator data.
Without an actual operating environment, it may be difficult to verify the operation.

Hello.
Did you introduce Aurora Heatmap before 5.7 and was able to collect data at that time?
The operation with WordPress 5.7 is not a problem, so it is considered to be another factor.
Please tell me more information about that.
I may be able to help.

Hello,
Thank you for your inquiry.
The movements of logged-in users are basically excluded because they interfere with the behavioral analysis.
The ability to customize data acquisition and viewing permissions is an upcoming development item.

However, please note that some of these features may be available in the premium version.

Hello.
By default, logged in users are excluded to avoid recording unwanted user behavior.
The current specification does not allow this to be changed arbitrarily.

Hello.
The comparison feature is an item currently under development.
However, this may be a feature of the paid version.
You could simply take a heatmap capture and then delete the data and re-measure it for comparison.

Hello.
I missed your question without a notification from the forum.
Sorry.
Have you resolved the issue?
Looking at the site, the measurement itself seems to be working fine.

I missed your question without a notification from the forum.
My apologies.
I’ll have to look at the content, but I think just inserting javascript in the shortcode is not enough in most cases.
You probably need to look at the whole thing, including the theme, etc., which is hard to do within the scope of free support.

Since this is a place to evaluate the free version, we won’t go into detail about the paid premium version, but you can install it with a dedicated plugin that you can download from the official website.
https://market.seous.info/en/aurora-heatmap/premium

Hello.
Thanks for the inquiry.
The phenomenon could be due to another plugin or theme defining the Mobile_Detect class of the same name.
To improve compatibility with caching, the User-Agent distinction on the Aurora Heatmap side has been modified to use the JavaScript in the browser.
Please check that you do not get a PHP warning like “There has been a critical error on your website” after upgrading to version 1.4.6.

Nice to meet you.
Thanks for the report.
We have released a new version 1.4.5 which fixes the error.
There is no problem in the previous versions except that an error is shown.
Please continue to let us know if you have any problems.

連絡遅くなりました。
ログイン中の管理権限所有者に限っても、ユーザーとパスワードの表示は危険だと思います。
公開プラグインとしてのセキュリティを考えると、実装は難しいという返答になります。