Tags are the collections of established tracking rules that you set up. A tag consists of a tag configuration, a trigger and variables may be present. A tracking rule consists of two questions: what is triggered and at what site interaction is it triggered. What is triggered is answered by the tag configuration. At which interaction this is activated is determined by the trigger.
But what are tag configurations, triggers and variables? And how do these work together within tag to control your tracking? In the image below, you can see how a tag is made up of a tag configuration, trigger and variables.
So in the tag configuration, you set what you want activated when the tag is triggered. This can be an HTML script, this can be the creation of an event for a third platform or configuration with a third platform or server. In the image above, this is an event created for GA4 with the event name "purchase.
A tag configuration is only triggered based on the trigger. Triggers determine when to fire a tag based on a specific site interaction such as page views, clicks or form submissions. In the image above, this is a trigger that is activated the moment a "purchase" event takes place in the site's DataLayer.
Variables are the dynamic elements that personalize your tags and triggers. They allow you to retrieve and use information such as page paths, user IDs or custom events from your DataLayer. For example, in the image above, the GA4 Measurement ID is a constant variable, the event parameters are also constant variables, and the variables under the values of the event parameters are retrieved from the DataLayer.
Through Google Tag Manager, you can set up tags on a Web container to track your site traffic through client-side tagging. But with client-side tagging, you won't be able to measure many of your conversions and events due to the interference of browsers, operating systems and AdBlockers. To get your tracking right you will need to implement server-side tagging. Your website data deserves the accuracy and flexibility offered by this advanced tracking method.
With this basic knowledge of tags, triggers and variables understood, you will be able to keep track of server-side tagging yourself after implementation. Let Adpage do the implementation for you, and with the knowledge above, you can then make that tracking setup all your own. Contact us to find out if AdPage can also set up server-side tagging for you.
There is no limit to the number of tags you can implement for your site using Google Tag Manager. However, it is wise to keep the number of tags as low as possible so that Google Tag Manager can continue to work optimally. Just like how your site gets slower from many different scripts, Google Tag Manager will also work less optimally with too many tags and triggers set.
Thanks to the use of tags on Google Tag Manager, tracking is moved from the user's browser to the Google platform. This puts less strain on your users' browsers, which have more capacity left over to load dje site faster. The amount of JavaScript code on the site is also minimized, improving performance.
A DataLayer is a JavaScript code that acts as an intermediary between your website and Google Tag Manager. To make specific data accessible through Google Tag Manager, it is recommended to install a DataLayer. Among other things, a DataLayer can temporarily store userinfo and productinfo which can be read and collected via Google Tag Manager.