Status codes

Every incoming and outgoing request in your Logs is tagged with an HTTP status code. To make debugging easier, Stape color-codes these status categories:

• 2xx (Success) – the request was successfully received and processed.
• 3xx (Warning) – redirects.
• 4xx (Warning) – client-side errors (issues with the request structure, container setup, or permissions).
• 5xx (Error) – server-side errors (issues on Stape's end or the destination server).

Here is an explanation of the most common status codes you'll encounter when troubleshooting your tracking setup.

• 200 (OK):

  • Incoming requests – your sGTM container successfully received the event from your website.
  • Outgoing requests – the third-party platform (such as Meta Conversions API, TikTok, or Google Analytics) received and accepted your data payload.

• 202 (Accepted) – the request was accepted for processing, but processing wasn’t completed.
• 204 (No content) – the request succeeded, but there is no body to return.

• 304 (Not Modified) – occurs when a web browser requests a tracking script (like your custom GTM loader) but the script hasn't changed since it was last cached, so the browser loads its cached local copy instead.
• 301 / 302 / 307 / 308 (Redirects) – these occur when an incoming request to your tagging server is forwarded or rewritten to a corrected destination path.

• 400 (Bad request) – the destination platform rejected your event, which generally points to a configuration issue within your tag – such as a missing required field, an invalid API token, or improperly formatted data parameters.
• 403 (Forbidden) – this typically points to a permission or setup mismatch. For example, in the Custom Loader power-up, you used your server GTM container ID instead of the web GTM container ID.
• 404 (Not Found):

  • Incoming requests – indicates that your tagging server can’t find or download your sGTM container configuration, which usually happens if the container is unpublished, deleted, or configured with an incorrect container ID on Stape.
  • Outgoing requests – the platform API endpoint URL set inside your sGTM tag is incorrect or has been deprecated.

• 500 (Internal Server Error) – indicates that the container or destination server has encountered an unexpected issue. In sGTM container, this often happens if a tag contains execution errors or is incorrectly modifying response codes.
• 502 (Bad Gateway) – indicates a network connection failure.
• 503 (Service Unavailable) – the destination platform’s server is temporarily unable to handle the request (for example, due to overloading or maintenance).
• 504 (Gateway Timeout) – your server-side container attempts to send tracking data to an external platform, but the platform fails to respond within the allowed timeframe.