Please help with Yandex Metrika

Thanks for the detailed report. I checked the script restoration code, and the documentation gave you the wrong attribute. I am sorry for the time this cost you.

Please replace data-faz-tag="analytics" with data-faz-category="analytics", keeping the type="text/plain" that you already used correctly:

<script type="text/plain" data-faz-category="analytics">
  // Put your existing Yandex Metrika JavaScript here.
</script>

Use this opening tag for your existing Metrika script; the comment above is only a placeholder for its JavaScript, not a complete tracking snippet. The documentation has been corrected.

Both attributes matter: type="text/plain" prevents the browser from executing the script before consent, and data-faz-category="analytics" tells the plugin which consent category controls its restoration. data-faz-tag is used for banner elements, not for this script-restoration mechanism.

With the correct tag, the plugin is designed to run the script when analytics consent is granted and on subsequent page loads while that stored consent remains valid. No custom event listener is needed for this tagged script. The fazcookie_consent_update event fires when the visitor changes their choice; it does not fire merely because a visitor with saved consent reloads the page. That distinction does not mean the saved consent has been lost.

On your first question: FAZ does not provide a setting that blocks access to the page until a choice is made. Scrolling or continuing to browse does not count as consent, so analytics requiring consent must remain blocked until the visitor explicitly agrees. A dialog offering both acceptance and refusal is not automatically the same as a cookie wall that requires acceptance to access the site; my earlier wording conflated those two cases.

To make the banner more noticeable, you can use the “Dim the page behind the banner” option in the banner settings. It provides a visual overlay without blocking interaction with the page. It is available for Box corner, Box centered and Full-width Banner layouts, and is disabled for the Classic layout.

One correction about reporting: the consent log records explicit consent choices, not individual visitors who saw the banner and never answered. If pageview tracking is enabled, the dashboard provides separate aggregate pageview and banner-view counts. Those counts do not identify unique visitors who ignored the banner and are not a replacement for Metrika analytics.

If the corrected tag still fails after a reload, please share your FAZ Cookie Manager version, the affected page URL and how the Metrika snippet is inserted (theme settings, another plugin or custom code), so I can investigate your specific setup.

• This reply was modified 1 week, 6 days ago by fabiodalez. Reason: Added the missing code example and corrected the explanations of consent, reporting and the original snippet