Ok, then it’s probably a plugin conflict with Statscounter, thanks for testing and trying! Is there an option in Statscounter to exclude it on certain pages? The problem will be that Bricks runs in the frontend and collides with the Statscounter JS there.
If there is an option to exclude on certain pages, you should exclude pages with the ?bricks=run parameter. This should solve the problem.
My client, who had this issue, contacted Statcounter support, and they fixed it by having the plugin disabled and the code manually inserted into Bricks → Settings → Custom Code → Body (footer) scripts.
They gave him the code snippet but I believe it can be generated from Statcounter’s account. Here’s how it looks:
<!-- Statcounter code -->
<script type="text/javascript">
var sc_project={placeholder:project-code};
var sc_invisible=1;
var sc_security="{placeholder:security-code}";
</script>
<script type="text/javascript"
src="https://www.statcounter.com/counter/counter.js"
async></script>
<noscript><div class="statcounter"><a title="Web Analytics"
href="https://statcounter.com/" target="_blank"><img
class="statcounter"
src="https://c.statcounter.com/{placeholder:project-code}/0/{placeholder:security-code}/1/"
alt="Web Analytics"
referrerPolicy="no-referrer-when-downgrade"></a></div></noscript>
<!-- End of Statcounter Code -->