Google Tag

The Google tag is a single piece of JavaScript, gtag.js, that you add to your website to send data to Google products. Google describes it as one tag that supports multiple products and services, and it sends website data to linked destinations to help measure your site and ads. You can configure it from inside Google Ads, Google Analytics, and Campaign Manager 360. Each Google tag has one tag ID, and you can connect that single ID to several destinations, so one install can feed several products. The tag ID is how everything connects. You copy it from Google Ads, Analytics, or another Google product, and the same snippet then serves all of them. Adding a new product later means connecting another destination in the interface, not editing the page.

Under the hood, the tag loads on each page and sends events, such as page views and conversions, to whichever destinations you have connected. A destination ID identifies the product that receives the data. For Google Ads the destination is your conversion tracking ID, and for Google Analytics it is the web data stream's Measurement ID. Tag IDs have prefixes such as GT, G, and AW. Google says the older global site tag has evolved into the Google tag, and if you already had a global site tag you do not need to update your site to use it. Tag IDs begin with prefixes that hint at their source, such as G for Analytics and AW for Google Ads. That is useful when you audit a site and find several different IDs, because each one belongs to a destination you can check.

Compared with Google Tag Manager, the Google tag is a code-first approach. Google's comparison says gtag.js needs one snippet per page, takes some JavaScript comfort to customize, and can only send data for Google products. Tag Manager takes two snippets, supports third-party and custom tags, and offers workspaces and version control. The Google tag works well with static sites, many content management systems, and hand-written HTML. Both are free. If your site only uses Google Ads and GA4, the Google tag is the simplest correct install. For a brochure site or a small shop on a hosted platform, a built-in integration often installs the Google tag for you. You still need to confirm it is configured with the right destinations and that no second copy is hiding in the theme.

Two failures account for most broken measurement. The first is leaving old conversion snippets on the page next to the Google tag, which can record the same sale twice. The second is putting the conversion event only where it never fires, for instance omitting the tag from the real confirmation page or firing the event on a page people can reload. Google also says that if you have more than one tag on your site, you can combine your Google tags for better data. Having several unrelated installs for the same destination causes confusion. Even a clean install can record a conversion on the wrong action. A tag on the confirmation page is only correct if the page loads once per real outcome and not when someone bookmarks or reloads it.

To check your install, use Tag Assistant and confirm your tag ID appears in the tags found header when you load a page. Then complete a test conversion and see that it shows up in Google Ads under the conversion action's status. This week, view the source of your confirmation page, count how many Google tags and conversion snippets are there, and remove duplicates. If you expect to add Meta, TikTok, or other vendor tags soon, that is the moment to consider moving to Tag Manager. Keep a short log of what you changed and when, so that a sudden drop in conversions can be tied back to an edit instead of guessed at.