How the Google tag works
The Google tag is one piece of JavaScript placed on every page of a site. Once it loads it can serve several Google products at the same time — Google Ads conversion tracking, Google Analytics 4, remarketing audiences — from a single installation rather than a separate snippet for each. It was previously called the global site tag, and the function it exposes in code is still gtag, which is why the two names are used interchangeably.
Every tag has an ID, and destinations can be attached to it. That means a tag installed for Analytics can also feed a Google Ads account without a second snippet on the page. Settings such as which domains count as one site, whether user-provided data is observed, and how a click identifier is stored are configured centrally rather than buried in page code.
Why the Google tag matters
It is the foundation everything else in Google measurement stands on. If the tag is missing from a page, nothing that happens there can be recorded: no conversion, no session, no audience membership. Most tracking problems I am asked to diagnose turn out not to be clever configuration faults at all, but pages where the tag never loaded — a checkout on a subdomain, a payment gateway that returns the customer to a thank-you page outside the main template, or a landing page built in a separate tool.
It also matters for bidding. Automated bidding learns from the conversions the tag reports, so a gap in coverage is not merely a reporting inconvenience. It teaches the auction the wrong lesson about which clicks deserve money.
Common mistakes with the Google tag
Installing it twice is the most frequent. Two copies usually mean duplicated pageviews and, where a conversion fires on page load, duplicated conversions — often because the tag was added to the theme and again through Google Tag Manager. The next most common is loading it after a consent script that blocks it silently, so it fires for some visitors and not others without anyone noticing.
The third is assuming installation equals tracking. The tag being present proves the page can talk to Google. It does not prove that a form submission, a phone tap or a purchase is being recorded as anything at all.
How to set it up properly
Install it once, site-wide, as early in the head as your consent setup allows, and prefer a single container-managed installation to snippets pasted into templates by different people over the years. Then check it with Google’s Tag Assistant on real pages, not just the homepage — walk the journey a customer actually takes, including any step that leaves your domain and comes back.
After that, confirm what the tag is being asked to send. A clean install feeding badly defined events is still bad data. If the site spans several domains, or a booking system sits elsewhere, settle cross-domain measurement before trusting any report, and keep a written note of which tag IDs exist and who owns them. A tidy tag management setup makes that far easier than a collection of hand-edited templates.