Stape/Documentation

How to fix error 403 (403 Forbidden - network)

Updated Mar 24, 2026

There are two reasons why you see a 403 error:

  1. You used Server container GTM ID when setting up a custom loader, instead of Web GTM ID. 
  2. You did not publish the initial version of the web container.
Wrong Custom Loader setup
Wrong Custom Loader setup
Error 403 when Server GTM ID is used instead of the web GTM ID
Error in the console

Another version of this error may appear if the system cannot find your Web GTM container.

System cannot find your Web GTM container
Google shows error 404, but the reason is actually the network error 403

Solution:

1. Check that you are using the correct Web GTM ID when generating the Custom Loader code. Adding the correct ID usually resolves the issue. 

To check the custom loader setting, log in to your stape.io account → open sGTM container → click Power Ups → open custom loader and check if you added Web GTM ID. 

Custom loader setting

Change the container ID to the Web container ID, click Save, and update the GTM script on your site.

To find your Web container ID, you need to open Google Tag Manager and select your web container. There you will be able to see the Web container ID.

2. Check that the web container has been published. Open your web Google Tag Manager container and ensure that it's published and running.

Comments

Can’t find what you are looking for?