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:
- Keep an option for request/response BigQuery logging at the tag level, or
- 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!