Knowledge for your website
Google Tag Manager: manage measurement code in a controlled way
Google Tag Manager manages tags and their triggers. It can simplify technical maintenance, but it replaces neither a measurement plan nor a review of the data a website actually transmits.
What are tags, triggers and variables?
A tag runs a defined integration, such as measurement code. A trigger specifies when this should happen. Variables provide the required values. These settings are managed together in a container.
Tag Manager is therefore a management tool. A configured analytics service evaluates the recorded events, for example Google Analytics. Installing it alone does not provide useful performance measurement.
How to check a change
- Describe the intended action: Which event should be recorded?
- Limit triggers: The tag should run only under the intended conditions.
- Compare existing integrations: The same measurement code must not unintentionally run in both the theme and the container.
- Use preview: Check the sequence before publication.
- Check the result: Compare the trigger with the data actually received.
Define responsibility and maintenance
Document a tag’s purpose, responsible people and the reason for a change. Remove unused integrations once their dependencies are clear. A small, understandable container is easier to check than a collection of unknown scripts. Also record how to reverse an erroneous change selectively.
Choices concerning data processing must also match actual behaviour. Integrating a service through Tag Manager does not automatically make it necessary or compliant with data protection requirements. A useful sequence connects marketing objectives and technical website maintenance.
Sources and further reading
When a server container can usefully handle additional work
With server-side tagging, a dedicated server container processes received measurement data and controls its onward transmission. The browser and its settings remain part of the data path. The Google architecture documentation describes the separation between incoming requests, processing and outgoing tags.
Assess a transition against a specific problem, such as unclear onward transmission to multiple services. A new operating environment also requires responsibility, cost control, monitoring and a documented return to the previous version.
| Check | Evidence before approval |
|---|---|
| Data path | Which fields arrive, which are removed and which are passed to which recipient? |
| Visitors’ choices | How is the current choice state transmitted and taken into account by every affected tag? |
| Operation | Who manages the domain, hosting, permissions, outages and running costs? |
| Acceptance | How are duplicates, missing events and differences from previous collection checked? |
Google also describes Consent Mode for server containers. The choice must be passed on technically; Consent Mode does not itself provide a banner. Server-side processing alone answers neither which data is permissible nor whether collection is complete. The checklist for cookies and integrations helps compare actual behaviour.
Relevant to your needs
Related topics
Online marketing
Online marketing for Swiss businesses: align your website, SEO, Google Ads and communications around a shared objective. Explore the approach.
Learn more
Web design
Websites for Swiss businesses: clear structure, mobile usability, understandable content and maintainable pages. Discuss a new website or a revision.
Learn more
Contact
Discuss your website, SEO or AI visibility with SEO & GEO Agentur Wittibschlager in Zürich. Contact details and useful information for your enquiry.
Learn moreYour next step
Let’s discuss
your website.
What should your website achieve for your business? Tell us about your plans.