25/ In April 2017, we got Approvals (GTM 360 only).
GTM 360 is the paid version of Google Tag Manager. Luckily the vast majority of features is available in the free version, too. Enterprise-level stuff like Approvals and extra Workspace quota is restricted to the paid offering.
From "not having to bother IT" to inspiring thousands of digital marketers to learn some JavaScript, GTM has been transformative in our industry of data, analytics, and marketing.
Follow me on this trip down memory lane! 2/ The original idea was to make it easier (and less error-prone) to deploy marketing scripts on a website. GTM did this by introducing "tags", "rules" (AKA triggers), and "macros" (AKA variables).
The original UI was unpolished, but the power of the tool was tangible.
Mar 24, 2022 • 6 tweets • 3 min read
Two very, very important releases to server-side #GoogleTagManager. One of them is arguably *the most important* update to the platform in a long, long, time, and the other opens up a myriad of use cases for data enrichment at scale.
Read on!
First, we have ASYNCHRONOUS VARIABLES and PROMISES.
In short, you can use *variables* to run asynchronous operations (such as send HTTP requests or communicate with BigQuery), and anything the variable is attached to *will wait for it to complete*.
The new Server container is now in public beta. You can create a new container in the Admin section of any Google Tag Manager account you have access to.
THREAD 1/11
Server-side tagging is (for now) a @GCPcloud managed environment, which serves as a server-side proxy for all your analytics, marketing, and advertising needs.
See this video for a walkthrough of how to set it up:
So, #GoogleTagManager introduced “server-side tagging”, at SuperWeek, which finally gives me a chance to unload some thoughts about it :)
Server-side tagging translates to a new “Server” container running on a cloud VM in your own domain namespace. 1/6
You send HTTP requests to it from the browser, and it parses these requests (using a new “Client” format), typically dispatching them to their respective endpoints server-to-server (e.g. Measurement Protocol). 2/6