Pro and Business plan users have access to logs. This feature is handy while setting up server-side tracking because you can see what data was sent, the request’s response code, as well as processed parameters so that any issues with your network or vendor won't go unnoticed.
For Pro and Pro+ users - logs for the last 3 days. For Business and higher plans - logs are available for the last 10 days.
There are four types of logs available: Access Logs, Request Logs, Response Logs, and Other Logs. All log types can be filtered by client, event name, response code, etc.
For example, you can check if all purchase events sent to Facebook received a 200 response code. This helps to ensure Facebook processed all purchase events successfully.
Logs are available only for Stape sGTM tags or Logger Tag. To see logs, you should enable it in tag settings. To do that, open the sGTM tag -> Scroll to Logs Settings -> Enable Always log to console.
To see logs, log in to your stape.io account -> Open sGTM container -> Click Logs. You can filter logs by Client name, event name, status, and date.
Quickly test and troubleshoot server-side tagging settings.
    1. Logs of Stape server Google Tag Manager tags.
Hosting your server Google Tag Manager on Stape is the best way to set up server-side tagging. Here's why...
Find out how to use server GTM Logs to troubleshoot common problems with server-side tagging. This includes an example of a real-world issue we ran into, and the steps taken to solve it via the logs.
Initially created by Simo Ahava, GTM Tools is now managed by Stape. Find out the tool’s benefits and how to use it.