5 Server Side Google Tag Manager Errors and How to Fix Them

Implementing a cloud tagging server with Google Tag Manager server side tagging can be tough. While it may seem overwhelming at first, you can sort this out with some technical knowledge and effort. Here are some of the common errors you might face when it comes to setting up your server and how you can solve them.

1. HTTP ERROR 400

Once you set up the tagging server for your google tag manager, you might like to open the tagging server URL in your browser. In this case, you might see a response “HTTP ERROR 400. Well, this does not mean there is some issue with your server-side GTM, but it simply means that no client has claimed the request.

So, you can test if your server is working or not by adding /healthy at the end of the tagging URL. Post that, you can open it in your browser.

Another way to check the proper functioning is to open the server GTM and test requests in debug mode. If you see that requests are coming into the sGTM debugger, the server was set up correctly. But, please note that you will see requests only if you have reconfigured them.

2. This site can’t be reached.

This error usually happens when you use a custom domain but have not set your DNS records your the subdomain or have done it incorrectly. Thus, you will need to wait for an average of 3-4 hours before DNS changes are applied. Besides, some providers even ask you to wait up to 72 hours.

There are many tools in the market in which you can paste your subdomain and check A or any other record. You will need to check if it points to the correct IP. If it is not accurate, you can check the DNS settings of your domain again.

3. Exceeded Billing Quota

Another error is when you exceed the free tier limit on GCP. There are two ways to handle this. Either you can exceed the number of testing environments or the free tier limit.

Google Cloud lets you have one testing server, GTM, in your account. So if you already have one, you will not be able to test the environment automatically. One way to sort this is by manually provisioning tagging server. Another way is to You should upgrade GCP to the production environment to solve these problems.

4. Your connection is not private

In this error occurs, there is an issue with creating an SSL certificate for your tagging URL. This might be due to a lack of time for issuing the certificate or any other issues with the certificate. We suggest you can wait for 30-60 minutes and then create an SSL certificate. If after 30 minutes you see the same error, you can contact your service provider.

5. 503 Service Temporarily Unavailable

This error means that your tagging server is down. For this, you will need to check your deployment status in the Google Cloud Platform. In most cases, you will need to contact your hosting support, and then you will be able to use your sGTM.

Wrapping Up

We hope this post helped you identify the most common problems with tagging servers and how to fix them. While you will be able to resolve some issues, others will need the help of your hosting provider.

Luckily, with Magic Pixel by your side, you can enjoy seamless server-side tagging and manage all issues along the way. So, schedule a demo today and connect with our experts to know more!