-
If I’m understanding your predicament correctly, you’re keen on tracking the response codes from Google’s data collecting point. But, you know what’s quirky here? In most circumstances, we don’t really tailor our monitoring in this way, especially when they don’t even step into your territory.
Usually, we keep things simple. We set up custom alerts in Google Analytics and it does the rest, notifying us if anything goes off course. A common alert we use is an unexpected drop in overall traffic compared to typical numbers – this way, we have a little birdie chirping in our ear when something’s amiss. You can find more details on setting up alerts [here](https://support.google.com/analytics/answer/9443595?hl=en).
However, if you still feel like enhancing your surveillance radar, it’d be more practical to track response codes from your own site, just to see if any error codes pop up for your visitors. Generally, this could be done by tagging error pages that your webserver spits out in response to errors. This works well if you’re coupling server-side GTM with frontend tracking; if you aren’t, then it’s a job for your backend developers to hook you up with.
