Google Tag Manager GA4 Setup: A Practical Guide for Business

A clean Google Tag Manager GA4 setup keeps your analytics in one container instead of scattered snippets inside your website templates. This guide shows a business owner in Uzbekistan what to install, which actions are worth tracking, and where most teams quietly go wrong.

Why pair Google Tag Manager with GA4

Google Analytics 4 tells you where visitors come from and what they do on your site. Google Tag Manager (GTM) is a free layer between the website and every tracking script. The container code goes onto the site once, and after that tags are added and edited in a web interface.

The practical gain is speed and independence. If you decide to run ads on Instagram or Google, the pixel and counters can be connected the same day rather than waiting in a contractor’s queue. That matters even more if your site is built on a constructor or maintained by an agency in another city.

Tags, triggers and variables in plain terms

Every rule in GTM is made of three parts. A tag is what gets sent, a trigger is when it is sent, and a variable is the data it carries, such as the page address or button text.

The full set of rules for your site is the container. Each change is published as a separate version, so if an edit breaks something, you can roll back to the previous one.

Step-by-step Google Tag Manager GA4 setup

Create an account and a container. GTM gives you two code snippets: one for the head section and one right after the opening body tag. They must appear on every page, through the template, CMS settings or a plugin. This is the only code change a developer has to make. Then follow this order:

  • Create a Google tag and enter your GA4 measurement ID
  • Attach a trigger that fires on all pages
  • Turn on Preview mode and confirm the tag fires
  • Publish a version with a clear description
  • Open the GA4 realtime report and find your own visit
  • Remove any old GA4 code left in the site template

Events that matter for a local business

Pageviews are only background noise. Revenue comes from actions, and customers in Uzbekistan more often call or message on Telegram than fill in a long form. Those are the actions to turn into events:

  • Phone number clicks — a trigger on links that start with tel:
  • Telegram clicks — links containing t.me
  • Form submissions — a form trigger or the success message appearing
  • Price list or catalog downloads — clicks on a PDF link
  • Clicks toward payment through Click or Payme — the payment button

Preview mode and the mistakes it catches

Before every publish, switch on Preview mode. It opens the site separately and shows which tags fired on which action. Keep GA4 DebugView open alongside it. This catches the usual problems: old analytics code still on the site, so data is doubled; a form trigger that fires on any button click, so reports show more leads than your CRM; and changes saved but never published.

Always compare the numbers with reality. If GA4 shows more enquiries than you actually received in Telegram or the CRM, look for a faulty trigger instead of celebrating growth. Order details such as value and products in an online shop are passed by the site itself through the dataLayer, and that part does need a developer.

Keeping the container tidy and safe

A container easily turns into a junk drawer, and every extra tag adds weight to the page. It can also run any script on your site, so publishing rights should go only to people who understand the consequences, especially outside contractors.

  • Use clear names for tags, triggers and variables
  • Describe every version: what changed and why
  • Delete tags that are no longer used
  • Recheck key events after every site update

When you don’t need GTM, and what comes next

For a simple site with one counter and no event tracking, or a builder that already has the integration you need, a container may be overkill. Once you add advertising, several counters and a need to count calls and leads, GTM saves time and reduces your dependence on developers.

The technical setup is only half the job. You still have to decide which actions count as goals and how they connect to sales. That is a marketing strategy question, and it is where markdev works with companies in Uzbekistan. If you want to talk through your analytics, get in touch and we will work out what to measure first.

FAQ

Do I need GTM if GA4 is already on my site?

Not necessarily. With few events and no advertising, a direct code is enough. GTM pays off when you track calls, Telegram clicks and forms, or connect several counters.

Why is my GA4 data doubled?

Usually GA4 is installed both as code in the site and through the container. Keep one method, remove the other, and recheck the realtime report.

Can I set up events without a developer?

Phone clicks, Telegram links, file downloads and many forms can be handled with triggers in the GTM interface. Order data normally needs a developer to push it through the dataLayer.

Who should have publishing access?

View and edit access can be wider, but publishing should be limited. A mistake in the container can affect the whole site.

Let’s look at your task for free

Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.