Google Analytics not running because of Chrome error ERR_BLOCKED_BY_ORB when retrieving https://www.googletagmanager.com/gtag/js?id=

Support Team posted this 09 June 2025

Hello,

Thank you for reaching out to us.

The ERR_BLOCKED_BY_ORB error in Chrome typically points to browser-level blocking, often related to Cross-Origin Resource Policy (CORP) settings or third-party script restrictions. This may not necessarily indicate an issue with Nicepage itself, but rather how Chrome is interpreting the embedded script request in certain environments.

That said, since the manual insertion of the full Google Analytics script in the <head> works correctly, the issue may stem from how Chrome handles automatic insertion via the Measurement ID field — possibly due to the way scripts are injected by the editor or page load timing.

To investigate further, could you please share:

The link to the published page where the issue occurs.
Whether you are using any browser extensions or strict security settings that may be interfering.

Meanwhile, using the manual method remains fully valid and does not impact the tracking itself, so feel free to proceed with that in the interim if needed.
...................................................
Sincerely,
Ahmad.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

65 Posts

rocket77 posted this 15 October 2025

I have also reported this problem and would really hope that we get another option for adding this. The script that nicepage writes does not really work properly. Besides that, the script is connected to "gdprConfirmed". But what happens when the GDPR Cookie option is not used on the site? For example, in America.

This is the code generated by nicepage when I add the GTAG in the site settings panel:

<script>
    function gdprConfirmed() {
        return true;
    }
    if (gdprConfirmed()) {
    --------------("\
    <!-- Google Tag Manager -->\
    <gascript>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':\
    new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],\
    j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=\
    'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);\
    })(window,document,'script','dataLayer','G-K3Q4MF4QM9');</gascript>\
    <!-- End Google Tag Manager -->\
    ".replace(/gascript/g, 'script'));
    }
    </script>

Does NOT work.

If I open the HTML file in an editor and replace the code with the code I get from Google it works fine.

This is the code from Google:

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());


  gtag('config', 'G-K3Q4MF4QM9');
</script>
<!-- Event snippet for Page view conversion page -->
<script>
  gtag('event', 'conversion', {
      'send_to': 'AW-17024544080/yyjmCMr-gr0aENDa97U_',
      'value': 1.0,
      'currency': 'USD'
  });
</script>

This DOES work.

If you would like Nicepage to be more widely accepted as an editor that agencies and web developers can use, I would please ask that you add a feature that allows for adding code to the HEAD section, AND at the very end right before the last closing tag.

I will be adding a post to the Wishlist relating to this.

Thanks!

Support Team posted this 20 October 2025

Hello PNV,

Please check the previous ticket on the same topic. It might be useful.
In general :
Both IDs added to the Site settings for Google Analytics and Google Tag Manager are being excess. Ids can be used only one at a time. In the case of using both, GTM ID only will be written in the code as a script.
To avoid this you can continue to input only GTM id to the Google-Site Settings and add your GA script to the HTML-Site Settings.
One more way is to deploy Universal Analytics with Tag Manager.

...................................................
Sincerely,
Anna.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

65 Posts

rocket77 posted this 20 October 2025

Thank you for your answer. However, this is not the main problem. The problem is that Nicepage is running a script to check to see if GDPR has been accepted, and only then does it run the code for GTAG.

If I turn off the cookie/GDPR feature provided by Nicepage, then Nicepage shouldn't add code with the function related to GDPR, it should just add the gtag code.

But Nicepage doesn't do that. Instead it runs this function:
function gdprConfirmed() {
return true;
on the page even if you don't use GDPR. So how can GDPR be confirmed if it is not being used?

Support Team posted this 20 October 2025

Hello PNV,

Thank you for your detailed explanation.
The gdprConfirmed() function is part of the general Nicepage script and is always included in the site code, even if the GDPR banner is disabled. However, when the GDPR feature is turned off, the function simply returns true by default and does not block or delay the execution of your GTAG or other scripts.

This means it will not affect how your tracking scripts run — it only ensures code compatibility for sites that have GDPR enabled.
This works only if you use Google Tag Manager ID only in the Google tab Site Settings as listed in another support message.
...................................................
Sincerely,
Anna.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp