Google Tag Manager for beginners: a small business guide

Google Tag Manager, or GTM, is a management layer. You add one piece of code to your website, then manage all other scripts through a web interface rather than your site’s code. Examples include Google Analytics measurement code, a Meta pixel, a LinkedIn tag, a chat widget or a Google Ads conversion tag.

Importantly, Tag Manager measures nothing itself. It is not an alternative to Google Analytics: it is the conductor deciding which script fires when. That confusion is the most common misunderstanding we encounter. Analytics is the report; Tag Manager is the wiring that feeds it.

Tag Manager is useful for small websites too. First check whether your site already has a container before adding another installation. Market share alone does not tell you which solution suits your site.

Tag Manager’s interface looks intimidating, but there are only four words you need to know:

Everything you do in Tag Manager combines these four: create a tag, attach a trigger and optionally use variables to send extra context. That is it. The rest is practice.

One more thing to know: changes only go live when you click Submit and publish a version. Until then, everything stays in a draft nobody sees. That makes experimenting safe, which is useful while learning.

A workable basic setup for an average small-business site takes half a day. Follow this route:

1. Create an account and a container at tagmanager.google.com. Choose Web as the platform. You receive two pieces of code that belong in the head and body of every page. WordPress, Shopify and Wix provide an official integration or a field for this.
2. Move Google Analytics into Tag Manager. Remove the separate GA4 code or analytics plugin, then create a Google tag with your measurement ID beginning G-. Never load GA4 through two routes at once, because every visitor will be counted twice.
3. Add your first real measurements. Most small businesses need three triggers: a phone-number click, for links beginning tel:, an email-address click, using mailto:, and a submitted contact form.
4. Test in preview mode. Click Preview, go through your site and check whether each tag fires when it should. Then check GA4 DebugView to confirm that the events actually arrive.
5. Publish and document. Give the version a name explaining what changed. In six months you will be grateful.

Testing is not a luxury. Around 40 percent of GA4 setups contain at least one incorrectly configured event. A tag that exists but never fires, or fires twice, looks just as tidy in the interface as one that works perfectly.

Consent Mode v2 gives Google tags signals about consent for analytics, advertising data and personalisation. Your cookie banner must correctly communicate the default status and the visitor’s choice. Google describes this in its Consent Mode implementation guide.

Measurement behaviour depends on configuration. In basic consent mode, Google tags stay blocked without consent. In advanced consent mode, tags can send cookieless signals. Google explains the difference between these configurations. A technical setting does not itself constitute legal permission.

An incorrect consent connection can make measurement incomplete. There is no universal loss percentage: inspect the effect in your implementation. Use Tag Manager consent settings and APIs to pass correct banner signals, and also assess tags lacking built-in consent checks.

Test both scenarios: accept cookies and inspect permitted measurement; refuse cookies and inspect remaining storage and network requests against your chosen, legally assessed configuration. Repeat after relevant banner or tag changes.

There is a development worth knowing about, even if you may not need to act today. Google broadly rolled out Google Tag Gateway in 2026, also called first-party mode. It loads Google scripts from your own .be domain rather than googletagmanager.com.

Why it helps: loading through your own domain changes the technical route of tags. This can reduce technical measurement loss, but does not guarantee that ad blockers or privacy browsers block nothing. Measure the effect on your site. According to the Tag Manager release notes, Google Cloud integration became generally available on 1 June 2026, followed by Amazon CloudFront on 3 June 2026, with Akamai, Fastly and Cloudflare earlier.

For small businesses, discuss this with your developer once the site uses a CDN such as Cloudflare. Without a CDN, it is not a priority. Remember: Tag Gateway makes measurement more complete but does not replace your banner. Consent remains consent.

These five keep recurring when we examine Belgian small-business sites:

1. Duplicate installation. GA4 runs both through a plugin and Tag Manager. Visitor figures are then roughly twice reality and the bounce rate unrealistically low.
2. Tags never published. Someone neatly built everything in a draft and forgot to click Submit. Measurement exists but is not live.
3. No consent connection. The banner and Tag Manager know nothing about each other. See the section above.
4. Names without a system. Tags named Tag 1 or Copy of Tag 3. Switching agencies can cost someone a day just working this out.
5. Measure everything, inspect nothing. The classic. According to Gartner, analytics influences only 54 percent of marketing decisions. More tags do not automatically improve decisions.

Tag Manager measures nothing itself. It decides which script fires when, and therefore whether your figures are right.

You can check a lot yourself, but an outside view helps. Want to know whether Tag Manager is set up correctly, your cookie banner sends the right signals and your conversions are actually measured? Run Marketing Scan’s free marketing scan. Within minutes you receive an overview of what works and what to tackle first, in everyday language.