Keep request/response BigQuery logging available (tag-level or via API

Stape feature request
1

Hey team,

First off, the new centralized Logs feature is a nice step, and I get the
maintenance argument for pulling hardcoded logging out of individual tags.

I wanted to flag one use case the in-tag BigQuery logging was quietly solving
for me, in case it can be preserved in some form.

As a partner, I manage conversion tracking across a lot of client sub-accounts.
The in-tag BigQuery logging let me stream the actual outgoing requests and the
platform responses (Google Ads, Meta CAPI, etc.) into BigQuery automatically. That
gave me one place to monitor tracking health across all clients, build alerts, and
catch issues before the client noticed.

The current alternatives don’t quite cover this one:

  • The centralized Logs feature is great for spot checks, but it lives in the web
    UI and gets reviewed per account. That’s hard to scale across dozens of containers.
  • The “Write to BigQuery” tag logs the event data in the container at tag fire,
    but not the raw request body sent to the platform or the response that comes
    back, which is exactly the part I rely on to verify delivery.

So the request is one of these, whichever fits your roadmap better:

  1. Keep an option for request/response BigQuery logging at the tag level, or
  2. Expose the request/response data from centralized Logs via an API or scheduled
    export, so it can be pulled into BigQuery programmatically across accounts.

Either one would let those of us managing many clients keep automated, centralized
monitoring without manual UI checks. Happy to share more about the workflow if
that’s useful.

Thanks for considering it!

2

Hi Alex,

Thanks for sharing this feedback and explaining your workflow in detail.

For this use case, I’d first recommend taking a look at Export Logs:

  • Log in to your Stape admin panel and select the container.
  • Navigate to Logs, then Export Logs.
  • To activate log export, toggle the switch and enter the required information to connect Stape Logs to your cloud storage

It allows you to automatically stream incoming and outgoing logs, including request and response payloads, directly to BigQuery or Cloud Storage. This can provide a centralized view across multiple client containers and help automate monitoring, alerting, and reporting without having to manually review each container’s UI.

Another option is to continue using previous versions of Stape tag templates. Since all Stape templates are open source, you can download an earlier version from GitHub and import it into GTM as a custom template. This will preserve the built-in BigQuery logging functionality that was available before the changes. The main tradeoff is that manually imported templates won’t receive automatic updates from the Template Gallery, so future maintenance would need to be handled manually.

That said, your point about monitoring request and response payloads across many client accounts is completely valid.

Thanks again for taking the time to share your feedback. It is very helpful as we continue improving the logging experience.