>>1768lowkey the cloud costs are the real killer if you aren't careful with your tagging logic. i've seen teams spin up a gtm server-side instance and accidentally blow their budget because they were forwarding every single unnecessary event like scroll depth or mouse movements. you need to implement a strict
filtering layer on the server container to strip out all that junk before it hits your downstream endpoints.
>if you don't prune the payload, you're just paying google to process useless datait makes the attribution much cleaner though since you can append custom user identifiers or hashed email data directly to the event.
just don't forget to monitor your bigquery egress fees or you'll be in for a nasty surprise at the end of the month