Skip to main contentSkip to footer

Google Tag Manager Setup

One organised, well-documented place to manage your website’s tracking tags, set up correctly, tested thoroughly and owned by your business.

Why Tag Management Matters

Modern websites carry many small pieces of tracking code: Google Analytics 4, Google Ads conversion tracking and remarketing, the Meta Pixel, LinkedIn Insight Tag, Microsoft UET, heatmap tools, chat widgets and more. When each is added directly to the website by different people at different times, through theme settings, plugins or pasted code, the result is often messy. Tags are duplicated, old tools keep loading long after they are no longer used, conversion events fire at the wrong moments, and nobody is quite sure what is installed or who has access. Every change requires a developer, and mistakes can break tracking silently for weeks.

Google Tag Manager, often called GTM, solves much of this by providing a single container installed on the website, inside which tags, triggers and variables are managed through a web interface. Marketing and analytics changes can be made, tested in preview mode, published as versions and rolled back if needed, without editing website code each time. Used well, GTM makes tracking more reliable, transparent and adaptable. Used carelessly, it becomes another layer of confusion, with unnamed tags, overlapping triggers and too many people publishing changes.

ViV Softech Solution is a website designing and digital marketing agency in Delhi. We set up and clean up Google Tag Manager for websites and landing pages for businesses across India, coordinating with your developers where needed. This page explains ownership and access, planning, the data layer, common tags and triggers, consent mode, testing, publishing and documentation. Google Analytics 4 configuration itself is covered on our Google Analytics 4 setup page.

What Our GTM Setup Covers

Ownership and Access

Account and container owned by your business, with sensible permissions.

Measurement Plan

Agreeing which actions to track and where.

Data Layer

Reliable data from your website for forms, ecommerce and more.

Tags and Triggers

GA4, Google Ads, Meta and other tags configured cleanly.

Consent Mode

Tags that respect visitor consent choices.

Testing and Documentation

Preview testing, versions and a written record of the setup.

Ownership, Access and Installation

Your Tag Manager account and container should belong to your business, created under a Google account your organisation controls, with a senior person holding administrator rights. Agencies and freelancers should be added as users with appropriate permissions, which you can remove at any time. Publishing rights are best limited to a small number of trusted people, while others can edit or view. We review existing access and remove users who no longer need it.

The container code is installed once on every page of the site, in the recommended positions, through a theme setting, a reputable plugin, or directly in templates. We check that it is installed only once, that old hard-coded tags are removed after migration to avoid double counting, and that the container loads on all relevant pages, including checkout and thank-you pages. For WordPress sites, we coordinate with any caching or optimisation plugins that might interfere with loading.

Planning and the Data Layer

Before building anything, we agree a measurement plan: which actions matter to your business, such as form submissions, calls, WhatsApp clicks, bookings, sign-ups and purchases; which platforms need to receive each action; and what details should accompany them, such as form name, service, order value, currency or product IDs. This plan prevents the common situation where tags are added piecemeal without a clear purpose. The data layer is the bridge between your website and Tag Manager. It is a structured way for the website to tell GTM what happened, for example that a form was successfully submitted or that an order of a certain value was completed with certain products. Relying on a proper data layer is far more reliable than triggering tags from button clicks or CSS selectors, which break when designs change and can fire even when actions fail. Ecommerce platforms such as WooCommerce and Shopify often have plugins or built-in options that push standard ecommerce events. Form plugins can push submission events. For custom sites, we provide clear specifications for developers to implement data layer events.

Common Tags and Triggers

Google tag and GA4 events

The Google tag for analytics, plus GA4 event tags for key actions, using consistent event names and parameters.

Google Ads

Conversion tags for primary actions, enhanced conversions where suitable, and the conversion linker for accurate attribution.

Meta Pixel

Base code and standard events, coordinated with any Conversions API setup for deduplication.

Other platforms

LinkedIn Insight Tag, Microsoft UET, Pinterest, Snapchat or others, only where you actively use them.

Engagement tracking

Clicks on phone and WhatsApp links, outbound links, file downloads and video engagement where useful.

Third-party tools

Heatmaps or chat widgets loaded thoughtfully, considering speed and consent.

Each tag has a clear trigger tied to a reliable event, and variables are reused rather than duplicated. See Meta Pixel and Conversions API.

Consent Mode and Privacy

Where your website uses a consent banner, tags should respect visitor choices. Google’s consent mode lets Google tags adjust their behaviour based on consent signals, and GTM’s consent settings can control when other tags are allowed to fire. Consent management platforms, many of which integrate with GTM, pass these signals. Google requires consent mode for certain features when serving users in the European Economic Area, and many businesses serving international audiences adopt it more broadly.

India’s Digital Personal Data Protection Act and its rules, as they come into force, also set expectations about notice and consent for processing personal data. We configure tags to align with your consent setup and privacy policy, avoid sending personal information such as names or phone numbers to analytics tools, and recommend legal advice for your specific obligations.

Testing, Publishing and Versioning

Preview Mode

Testing every tag and trigger with Tag Assistant before publishing.

Versions and Notes

Each published version named and described, so changes can be traced and reversed.

Platform Verification

Confirming data arrives correctly in GA4, Google Ads and Meta.

We test on real devices, submit test forms and place test orders where relevant, and check that each conversion is counted once. Workspaces can separate ongoing changes so incomplete work is not published accidentally.

Cleaning Up Existing Containers

Many businesses already have a Tag Manager container that has grown untidy over time. A clean-up starts with an inventory: every tag, trigger and variable, what it does, whether it still fires, and whether the tool it serves is still in use. We identify duplicates, such as GA4 configured both in GTM and through a plugin; outdated tags, such as old Universal Analytics tags or pixels for platforms you no longer use; triggers that fire too broadly, such as conversion tags on every page view; and missing tags for actions that matter. We then rationalise the container with consistent naming conventions, folders, reusable variables and clear notes, removing what is not needed and fixing what is broken. We pause or remove tags carefully, verifying in preview that important tracking continues working. A cleaner container loads faster, is easier to maintain, and produces more trustworthy data. See landing page speed improvements.

Documentation and Handover

We document the setup in plain language: which tags exist, what triggers them, which platforms receive which events, which data layer events the website must keep sending, who has access, and how to test changes. This documentation helps your developers avoid breaking tracking during website updates, helps new team members or agencies understand the setup quickly, and makes troubleshooting faster. We also recommend a simple change process: changes tested in preview, published with descriptive notes, and checked in the receiving platforms afterwards. Server-side tagging, which moves some tag processing to a server you control, can improve data reliability and site performance, but adds hosting cost and complexity; we discuss whether it suits your situation rather than recommending it by default.

Our Process

We review existing tags, installations, access and tracking issues.

We agree a measurement plan and data layer requirements.

We configure tags, triggers, variables and consent settings.

We test thoroughly, publish versions and verify platform data.

We document the setup and hand over clear guidance.

What Affects Cost

  • Number of platforms and events tracked.
  • Website platform and data layer work needed.
  • Existing container clean-up.
  • Consent management integration.
  • Server-side tagging, if chosen.

Frequently Asked Questions

Not always, but it makes managing several tracking tools easier and more reliable.

The standard version is free. Server-side tagging involves hosting costs.

The container itself is light; the tags inside it matter more. We keep containers lean.

Yes, through theme settings, plugins or templates.

Your business, with agency access you can remove.

Yes, through an audit and careful clean-up with testing.

Bring Order to Your Tracking

Tell us about your website and tracking tools. We will review your setup and share a clear quote.

Call NowWhatsApp