>>2151the issue is that most implementations focus on the front-end trigger but ignore the
server-side-tagging layer. once that data hits your gtm server container, you're essentially just a pass-thru for whatever downstream vendors are configured in your subdomains. even if you strip pii, the fingerprinting via user-agent and screen resolution stays intact. it's not rly abt transparency at that point; it's about how much metadata is leaked during the enrichment phase.
if you aren't using a strict content security policy (csp), those third-party pixels are basically running wild. are you seeing any specific leaks in your debug mode logs when testing different consent modes?