GA4 vs Google Tag Manager: Setting Up Website and Conversion Tracking

Google Analytics 4 (GA4) and Google Tag Manager (GTM) are not competitors: GA4 is the reporting tool that stores and analyses your visitor data, while Tag Manager is the control panel that decides which tracking code runs on your site and when. You can run GA4 without Tag Manager, but once you track leads, sales, ads and consent together, most business sites are easier to manage with both.

This guide is for owners and marketers who want tracking they can trust: which tool does what, how conversions and e-commerce events are counted, what consent mode v2 changes, and where Meta's Pixel and Conversions API fit.

#What GA4 and Tag Manager each do

The simplest way to see the difference: GA4 is where data ends up, and Tag Manager is how it gets sent.

A few Tag Manager words come up often. Google's own help defines a container as the collection of tags, triggers, variables and settings installed on one website or app. A tag is a piece of tracking code, such as the GA4 tag or a Google Ads conversion tag. A trigger is the rule for when a tag fires, for example "when the thank-you page loads" or "when the enquiry form is submitted". A variable is a value a tag reads, such as the order total.

If you want to understand which GA4 numbers are worth your time, my guide to Google Analytics 4 for business owners covers the reports. This article is about the setup underneath them.

#Do you need Tag Manager, or is GA4 enough?

Google gives three ways to add GA4 to a site: paste the Google tag into every page, use your website builder's built-in GA4 setting, or add the GA4 tag through Tag Manager. All three collect basic page views and the automatic events GA4 records on its own.

GA4 on its own is usually enough when:

• The site is small, you only need traffic and page views, and nobody runs paid ads.
• Your platform (Google names Wix and Duda as examples) has a solid built-in GA4 connection that already sends the events you care about.
• Nobody on the team will maintain tracking after it is set up.

Tag Manager earns its place when:

• You run Google Ads, Meta ads or LinkedIn ads and need each one to see the same conversions.
• You want to track form submissions, phone and WhatsApp clicks, file downloads or booking widgets.
• You need a cookie banner that actually controls which tags fire (more on consent below).
• Marketing changes often and you do not want to touch site code each time.

One warning applies either way. Google says not to add more than one Google tag to a page, and the most common tracking fault on business sites is double counting: GA4 installed by a plugin and again through Tag Manager, so every visit and sale is recorded twice. Pick one method and remove the others.

#How a tracked conversion travels

Before any setup, it helps to see the chain a single enquiry or sale passes through. A break anywhere in it means a lost or doubled number.

The consent check comes first, because tags must respect the visitor's choice before sending anything. The trigger decides the action counts, the key event setting tells GA4 it matters, and Google Ads can then create conversions from it, linking ad spend to real leads and sales.

#Key events: telling GA4 what a lead or sale is

GA4 records many events automatically, but it does not know which of them matter to you. You mark the important ones as key events (GA4's current name for what most people still call conversions). Google's help says a standard property can have up to 30 key events, and Analytics 360 up to 50. Marking an event as a key event only affects data from that point on; it does not rewrite past reports.

Good key events for a business site are few and clear:

1. A successful enquiry form submission, fired on the thank-you message or page, not on the button click.
2. A click on a phone number or WhatsApp link.
3. A booking or quote request completed.
4. For stores, a completed purchase.

Google Ads conversions created from GA4 key events are reported in Google Ads and in GA4's Advertising section, not in GA4's standard reports, so do not expect every number to match.

#E-commerce tracking: the events that drive revenue reports

For an online store, GA4's revenue, product and funnel reports depend on a set of recommended e-commerce events sent with the right details. Google's developer guide lists them, including:

The purchase event matters most. Google states that transaction_id is required for purchases and refunds, and that currency must be set whenever a value is sent. The value should equal the total of price times quantity across the items. Without a unique transaction ID, a customer who refreshes the order confirmation page can be counted as a second sale.

Most store platforms have apps or plugins that send these events, and they are a sensible starting point. Check them before trusting them: place a test order and confirm one purchase arrives in GA4's DebugView with the correct total and currency. If shoppers leave at checkout and you want to know where, my article on why checkouts lose sales shows what the funnel events can reveal.

#Consent mode v2 and cookie banners

Consent mode is how Google tags adjust to a visitor's cookie choice. Google updated it in November 2023 to version 2, which added two settings to the original two:

Google ties version 2 to its EU user consent policy for visitors from the European Economic Area (EEA). If your site gets EEA visitors and you use Google Ads, you need a consent banner that sends these signals. Google treats a missing signal the same as "denied", so when nothing is sent, remarketing gets no data and conversion measurement is limited.

There are two ways to run it:

• Basic: Google tags are blocked until the visitor agrees. Nothing is sent for people who decline.
• Advanced: tags load first and, if the visitor declines, send cookieless pings without setting cookies. Google uses these for behavioural and conversion modelling to fill gaps in reports.

Google notes that with basic consent mode you do not get its full benefits. Which one to use is a legal and policy decision for your business, not just a technical one. Tag Manager helps here: its Consent Initialization trigger fires before every other tag, and each tag can be set to need specific consent before it runs. Many consent banner tools have Tag Manager templates in Google's Community Template Gallery.

For Indian businesses, India's own data law adds consent and notice duties of its own. My guide to the DPDP Act for website owners explains what applies to forms and tracking.

#Meta Pixel and Conversions API at a glance

If you run Facebook or Instagram ads, Meta has its own tracking alongside Google's. The Meta Pixel runs in the visitor's browser. The Conversions API sends the same events from your server, platform or CRM directly to Meta, so data still arrives when browsers or ad blockers stop the Pixel.

Meta recommends using the Conversions API alongside the Pixel. When both send the same event, you must set up deduplication: the Pixel's event name and event ID must match the server event's event_name and event_id. Meta only deduplicates events that arrive within 48 hours of each other. Get this wrong and every sale is counted twice, which makes your ad results look better than they are.

Tag Manager can run the Pixel and, through server-side tagging, can also feed server events. Server-side tagging runs a Tag Manager container on a server you control, such as a Google Cloud project, which gives more control over what data leaves your site. It also adds hosting and upkeep, so it suits businesses with real ad spend rather than every small site.

#What a proper tracking setup includes

Whoever sets up your tracking should be able to show you each of these:

• One installation method for GA4, with no duplicate tags.
• A short written list of key events and what each one means in business terms.
• Lead events that fire on success, tested with real form submissions.
• For stores, purchase events with unique transaction IDs, correct value and currency, tested with an order.
• A consent banner that controls tags, with consent mode v2 signals where EEA visitors or Google Ads require them.
• Google Ads conversions created from GA4 key events, or a clear reason they are not.
• Meta Pixel and Conversions API with deduplication, if you run Meta ads.
• Admin access to GA4 and Tag Manager in your own business Google account, not the developer's.

#When to get help

You can install GA4 alone in an afternoon, and for a small brochure site that may be all you need. Get help when ad spend depends on the numbers, when the store's revenue in GA4 does not match your real orders, when you serve visitors from Europe, or when you suspect events are counted twice. Fixing bad tracking later is harder, because the wrong data is already in your reports and cannot be corrected backwards.

My analytics and tracking setup service covers GA4, Tag Manager, consent mode, e-commerce events and ad platform tracking, with a written list of what is tracked. Once the data is right, conversion rate optimisation is how you use it to win more leads and sales.