Container logs
Updated July 2026 · 1 min read
Logs record the requests your container receives, so you can check what arrived and spot errors — even when you weren't watching in real time.
Find the logs
Open your container and go to the Logs tab. Each entry is one request the tagging server received, with details like the time, the request path and the response status. Use the filters above the list to narrow entries down.
Logs vs preview
- Preview is live: you trigger events and watch them arrive in the moment.
- Logs look back: what did the container receive an hour ago, or overnight?
Use Preview & debug mode while you set things up, and logs once traffic is flowing on its own.
What to use them for
- Confirm events keep arriving. After launch, a quick scan of recent entries shows your tags are still sending — no test events needed.
- Spot errors. Entries with an error status (4xx or 5xx) point at requests the server couldn't handle. See Common error codes for what each range means.
- Pin down gaps. If a platform reports missing conversions, the logs show whether the events reached your container at all — which tells you whether to debug the sending side or the GTM server container.
Logs show that a request arrived and how the server answered — not how tags processed it. For tag-level detail, use Google Tag Manager's server preview.
Logs are kept for a limited period, so don't treat them as a permanent archive. If you're chasing an intermittent issue, check the logs soon after it happens.