Logs feature
Updated Mar 28, 2025
The Logs feature provides real-time and historical records of the data flowing in and out of your server-side Google Tag Manager (sGTM) container. Logs make it straightforward to monitor and troubleshoot your server-side tracking setup so that any issues with your network or vendor don’t go unnoticed.
The Logs feature is available for Pro, Business, and Enterprise server-side GTM subscription users:
- Pro - last 3 days’ logs.
- Business - last 10 days’ logs.
- Enterprise - last 10 days’ logs.
Benefits of the Logs feature
- Quick troubleshooting & error detection - logs make it easy to identify and resolve issues in your server-side tracking setup. By reviewing the status codes (e.g., 200, 400) and other parameters, you can quickly see why certain events are failing or succeeding.
- Validation of data accuracy - with visibility into requests and responses, you can confirm that critical events (like “purchase”) are successfully being sent and processed by platforms such as Facebook, ensuring your analytics and ad tracking remain accurate.
- Improved debugging during setup - setting up server-side tracking can be complex. Logs provide detailed insights at each step, minimizing guesswork and speeding up configuration and testing.
- Verification of vendor & network performance - if a platform (e.g., Facebook) is experiencing delays or rejects certain requests, logs will show the response codes and any error messages, enabling you to address or escalate issues quickly.
- Centralized monitoring - all relevant tracking information resides in one place, making it easier for teams to collaborate on troubleshooting and performance optimization.
How to use Logs
1. Log in to your stape.io account.
2. Select your sGTM container on the dashboard.

3. Open the Logs tab.

4. Configure your Logs request:
- Type of logs:
- Access Logs - these logs display the requests that your GTM server has received. Please note that they don’t contain cookies or personally identifiable information (PII).
- Request Logs - these logs display the requests your server has sent to platforms like Facebook or TikTok. This only works if you use Stape tags for these platforms and have enabled the respective settings.
- Response Logs - these logs display the responses your server has received from platforms such as Facebook or TikTok. This only works if you use Stape tags for these platforms and have enabled the respective settings.
- Other Logs - these logs cover the requests that don’t fit into the other three categories. For example, logs generated by the Stape Logger tag will be displayed here
- Date and time - select the time period for which you want to receive the logs.
- Request parameters - these allow you to filter your logs to find the ones you’re interested in. Different types of Logs offer different parameters, such as Status (the logs’ request code), Client (the logs’ origin), or Platform (that sent or received the logs).
After that, click Show logs.

5. You will see the list of all logs that fit your request. You can download the data by clicking Download as CSV or click on any log record to expand to Detailed view.


Set up Logger Tag in sGTM
The Logger tag is available in the server Google Tag Manager template gallery and is extremely helpful for testing POST requests in sGTM. For example, if you’ve noticed that some purchases in Google Analytics miss purchase value, the Logger tag can help troubleshoot this error (by setting up a tag that triggers the purchase event when the purchase value is 0).
1. Download the Logger tag from GitHub → open the Templates sections in the server Google Tag Manager container → click New.

2. Click three dots in the top right corner → click Import → select the Logger tag template you’ve downloaded from GitHub → click Save.

3. Create a new tag in sGTM → tag type Logger Tag → select if you want to log events only while debugging or always → select what information you want to add to logs → add event name (static or dynamic) → add custom data if needed → add a trigger.

4. Launch sGTM debugger and test the Logger tag. Once the tag is triggered, go to your sGTM Container → click Logs → click Other logs → add event name → click Apply filter. You will see the information about requests and can troubleshoot any issues.

Testing the Logs feature
To verify that the Logs feature is working properly, perform actions on your website that are supposed to trigger your configured events and then check whether these events appear on the Logs dashboard.