How can we help?

Most common errors and their solutions

  • Updated

1. Error 404

That means we can't download the configuration of your sGTM.
That can be because of:
- sGTM container is deleted
- sGTM container not published
- You use the wrong configuration code
If none of the above issues exist, we recommend creating a new sGTM container and using it. You can utilize export and import functionality to migrate your existing configuration.

2. Error 403


Make sure that you're adding the Web GTM container id and not the server GTM container id.
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.




Usually occurs when a request is blocked by something, e.g. Chrome Developer Tools or an ad blocking plugin.
Try to check if error still appears in incognito mode or in another browser.
Also, try to disable all extensions in your browser and check if error is still present.




Error usually occurs when a request is blocked by the browser’s tracking prevention.
Check if you are sending request to Google Ads or any other tracking service with correct consent settings.
Also check if ​dma_cps parameter is present in the request url and set to ​dma_cps=sypham.

5. Error 500


You can receive 500 in cases when some tag changes the response code. For example, in case there was an error in some tag. 
Looks like you sent requests with a preview header and tried to debug something.

6. Error: 190~1464


Facebook recommends removing affected pixels and re-adding them to your CAPI Gateway hub. Basically, you would need to reauthorize affected pixels.


7. Error: 400


400 response for tagging server URL is correct behavior. 
To check if tagging server URL works correctly, you should add /healthy at the end of the URL. If the response is ok, then tagging server URL worked correctly. 



Was this article helpful?

0 out of 2 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.