Hi @wpbluefox,
Thanks for reporting this issue. It seems something wrong with capturing that data. I’m trying to understand if it causing by the plugin or the metrica settings.
Our colleague also wants to track scrolling info, as far as I know, this feature is not supported by Yandex Metrika plugin.
How to implement this feature?
Maybe add original Yandex code, or part of it to the website?
Could you give us some idea?
I think that functionality depends on the “webvisor” Did you activated it?
Hello there,
Thanks for reply!
Everything is enabled, except for tracking hash in address bar:
https://prnt.sc/x5tcxk
Webvisor is enabled as well.
Can it be caused by firewall we use?
We use All in One Security plugin,
and Perishablepress 6G or 7G firewall.
Can it be caused by firewall we use?
We use All in One Security plugin,
and Perishablepress 6G or 7G firewall.
I haven’t verified this idea yet but I’m suspicious about the CSP configuration – https://yandex.com/support/metrica/code/install-counter-csp.html#install-counter-csp__urls
Hi @wpbluefox,
I’ve checked this one of my sites and unfortunately, I couldn’t see click maps. The Session Replay’s are working fine, which is also depends on the webvisor settings, so I’m curious if this is something related to Metrica’ itself.
You might give it a try to Yandex’s snippet rather than using the plugin but I don’t think that would fix the issue here.
I’m still thinking this might be related to CSP header, perhaps it’s not a bad idea to inject those headers within the plugin. (maybe in the next version)
I think our marketing colleague mentioned that Session Replay’s are working fine for us too.
So have I understood it correctly, that you think you may get Click map fixed soon in one of next updates,
And Scroll map … ?
Hey @wpbluefox,
I understood the root cause of the problem. Do you see something like https://cloudup.com/c4w0yr3B3vi on the console when you try to access maps?
I had that problem on my site and fixed by removing the “X-Frame-Options” header. I don’t think the plugin can solve such problems. It happening because webvisor trying to open your site in the iframe.
When you have “SAMEORIGIN” directive, the page can only be displayed in a frame on the same origin as the page itself. So, you can’t see it on webvisor.com domain.
I’m marking this topic as resolved since nothing much to do at this point.
