Is Your Google Tag Manager Actually Working? How To Find Out

This blog post includes insights from Craig Haller, Director of Digital Marketing at Astute. He has almost a decade of experience auditing and rebuilding GTM, GA4, and Google Ads tracking setups for clients across healthcare, home services, and other lead-gen industries.

Google Tag Manager is installed. Google Analytics is collecting traffic. Google Ads shows conversions.

Everything must be working, right? Not necessarily.

A Google Tag Manager container can be present across your website while important form submissions go unrecorded, calls lose their attribution, and the same lead gets counted two or three times. The installation may be working perfectly while the measurement system built around it is not.

“The biggest pattern is false confidence,” said Craig Haller, director of digital marketing at Astute. “Most sites I inherit don’t have good tracking. GA4 is collecting data, Google Ads has conversions coming in, GTM is installed, so everyone assumes they’re covered.”

That assumption can quietly distort campaign performance, lead quality, and return on ad spend. Before you trust the numbers, you need to know what Google Tag Manager is actually being told to track.

How Can You Tell if Google Tag Manager Is Working?

Google Tag Manager is working properly when each important action on your website:

Gets captured after it successfully happens
Gets counted the correct number of times
Appears under the right event name
Reaches the intended analytics or advertising platform
Retains useful source and campaign information
Can be connected to a real lead or business result

Seeing the GTM code on your website only confirms that the container was installed. It does not confirm that the tags, triggers, events, and platform connections inside that container are accurate.

That requires testing the complete path from the website interaction to the final report.

What Does Google Tag Manager Actually Do?

Google Tag Manager, often shortened to GTM, gives marketers one place to manage many of the tracking codes used across a website. Instead of hard-coding every analytics script, advertising pixel, or conversion event into the site, teams can configure and publish them through the GTM interface.

A basic GTM setup includes three main parts:

Tags send information to platforms such as Google Analytics or Google Ads.
Triggers determine when a tag should fire, such as after a page loads, a form is submitted, or a link is clicked.
Variables provide additional information, such as the page URL, form ID, button text, or campaign details.

Google Tag Manager listens for an action that meets the conditions of a trigger. It then fires the corresponding tag and sends the information where it needs to go.

That makes GTM useful, but it does not make it automatic.

“GTM only does what it’s told,” Haller explains. “If the setup is sloppy, outdated, or untested, it can send bad data into GA4, Google Ads, and the other platforms you’re using to make decisions.”

GTM is the delivery system. It cannot decide which actions matter, recognize that a form has changed, or determine whether an event was configured correctly.

Why Does GTM Fail Even When It Is Installed?

Most GTM problems do not begin with one dramatic technical failure. The setup gradually drifts away from the website it was built to measure.

A form platform changes. A landing page gets rebuilt. A new call-tracking provider is introduced. Someone adds another Google Analytics tag without realizing one already exists. An old conversion remains active after a campaign ends.

The website evolves, but its tracking doesn’t always evolve with it.

“The most common issue is that GTM gets installed, but no one really owns the setup after that,” says Haller. “Tags are added over time. Events get renamed. Form platforms change. Landing pages get rebuilt. But the tracking doesn’t always get updated with it.”

Common causes of GTM failure include:

Triggers that rely on outdated form IDs, page URLs, or button classes
Analytics code installed directly on the site and again through GTM
Tags firing on a button click instead of a successful form submission
Thank-you pages that can be refreshed or visited directly
Forms embedded through third-party platforms that behave differently
Legacy tags that continue running after a platform or campaign changes
Consent settings that block or release tags at the wrong time
New pages that were never included in the original setup

Google provides consent controls and a Consent Overview within GTM, but those settings still have to be configured and tested correctly. Consent mode changes tag behavior based on the choices submitted through a website’s consent banner.

A container can therefore load successfully while the tags inside it fire incorrectly, inconsistently, or not at all.

Which Website Events Should You Be Tracking?

For a lead generation website, the most valuable events are actions that show meaningful intent.

These often include:

Successful form submissions
Tracked phone calls
Meeting or consultation bookings
Quote requests
Qualified live-chat leads
Click-to-email actions
Completed applications
Visits to a confirmation or thank-you page

These actions usually indicate that someone moved beyond browsing and attempted to contact the business.

GA4 refers to important business actions as key events. When one of those actions is also used to evaluate or optimize advertising, it can be created as a conversion in Google Ads.

That distinction matters because not every website event should influence advertising decisions.

Scroll depth, video views, page views, button clicks, and time on page can provide helpful context. They may show that someone engaged with a page. They do not necessarily show that the person became a lead.

These engagement signals matter for a different reason too — they’re part of what makes a website effective in the first place, separate from whether your tracking setup is accurate.

Common mistakes we see

“The mistake is treating every interaction like a conversion,” Haller says. “If you send too many weak signals into GA4 or Google Ads, you muddy the data and make it harder to optimize around what actually matters.”

A visitor clicking a form button, for example, does not guarantee that the form was submitted. The form may have returned a validation error because a required field was blank.

A useful tracking plan separates actions into two categories:

1. Primary Conversion Events

These are the actions most closely connected to leads or revenue. They may be used for campaign reporting and bidding.

Examples include completed forms, qualified calls, booked meetings, and submitted quote requests.

2. Supporting Engagement Events

These help explain how visitors use the website but do not represent completed leads.

Examples include scrolls, video plays, navigation clicks, form starts, and downloads.

Both categories can be valuable. Problems begin when they are treated as if they mean the same thing.

7 Signs Your Google Tag Manager Setup May Be Broken

Tracking problems are not always obvious. The data may look believable enough that no one thinks to question it.

These signs deserve a closer look.

1. GA4 and Google Ads Tell Very Different Stories

The platforms will not always report perfectly identical numbers. They may apply different attribution rules, reporting windows, or conversion settings.

Large or unexplained gaps, however, can point to missing events, inconsistent conversion definitions, or broken connections between platforms.

2. Your Lead Reports Do Not Match Your Actual Leads

Compare website conversions against form notifications, call-tracking records, meeting bookings, and CRM entries.

If GA4 reports 300 leads and the business received 140, duplicate events or weak conversion definitions may be inflating performance.

If the website received 140 leads and GA4 shows 60, important actions may be missing.

3. One Form Submission Produces Multiple Conversions

A single submission can trigger several events when tracking is installed in multiple places.

For example, the form platform may send an event directly to GA4 while GTM sends another. A thank-you page trigger could then record the same action again.

The reports show three conversions. The sales team received one lead.

4. Form Tracking Relies Only on Button Clicks

Click tracking can be useful, but a click is not always a completed action.

A button-click trigger may fire even when the form fails validation, the submission returns an error, or the visitor abandons the process. GTM also offers form submission triggers that can check whether a form was successfully sent, although the right approach depends on how the form is built.

5. Calls Are Counted but Not Attributed

Knowing that a call happened is helpful. Knowing what produced the call is far more useful.

A healthy setup should preserve as much source, campaign, landing-page, and keyword context as the call-tracking platform allows. Otherwise, teams may know the total call volume without knowing which marketing generated it.

6. No One Knows What Half the Tags Do

Names such as “Form Tag New,” “GA Event 2,” and “Test Conversion Final” are warning signs.

A clean GTM container should use consistent names that clearly indicate the purpose of each tag, trigger, and variable. Old tests and inactive tags should be documented, paused, or removed.

7. No One Owns Tracking After Launch

GTM requires maintenance because the website and marketing strategy continue to change.

“Most bad setups aren’t broken because of one huge mistake,” says Haller. “They’re broken because the garden is untended.”

When no one owns testing, documentation, and updates, small issues accumulate until the reports can no longer be trusted.

How to Test Whether GTM Is Tracking Conversions Correctly

A proper test should follow one action from beginning to end.

Do not stop after confirming that a tag fired. Make sure the action appeared once, under the right name, in every platform where it is supposed to appear.

1. Define the Action You Are Testing

Start with a specific business result, such as:

A visitor arrives through a paid search ad, completes the contact form, and reaches the confirmation page.

Identify what should happen at every stage:

Which event should GTM detect?
Which tag should fire?
What should the event be called in GA4?
Should it be marked as a key event?
Should it become a Google Ads conversion?
Should the original campaign information remain attached?

This gives you a clear expected result to test against.

2. Use GTM Preview Mode and Tag Assistant

GTM’s Preview mode connects the website to Tag Assistant. It shows which tags fired, which did not fire, the order in which they ran, and the event that triggered them.

Complete the action as a real visitor would. Then check:

Did the correct tag fire?
Did it fire only once?
Did it fire after the action succeeded?
Did any unexpected tags fire?
Did the event include the necessary variables or parameters?

Repeat the process across different forms, devices, landing pages, and browsers when relevant.

3. Confirm the Event in GA4 DebugView

A tag firing inside GTM does not automatically prove that GA4 received and processed the event.

GA4’s DebugView displays events as Analytics collects them in real time. This allows you to confirm the event name, parameters, and sequence while troubleshooting the implementation.

Check that the event appears once and contains the information your reporting depends on.

4. Review the Google Ads Conversion Settings

Confirm that the correct event is connected to Google Ads and that its settings reflect how the business wants to measure leads.

Review details such as:

Whether the conversion is primary or secondary
Whether it is included in campaign goals
How repeat conversions are counted
Which attribution settings apply
Whether the conversion is being used for bidding
Whether an older version of the same conversion remains active

Google Ads can optimize bidding around conversion signals created from GA4 key events. That makes the quality of those signals especially important.

5. Compare Tracking Data With Real Lead Records

The final test happens outside GTM.

Compare the events against:

Form notification emails
Call-tracking records
Scheduling platform bookings
Chat transcripts
CRM records
Sales or admissions reports

This comparison helps you find events that are missing, duplicated, or technically successful but disconnected from actual lead activity.

As Haller puts it, “Is that action being captured? Is it being counted once? Is it showing up in the right place? Do we know where it came from?”

Those are the questions that determine whether the tracking is useful.

How Does Bad GTM Tracking Affect Google Ads?

Google Ads learns from the conversion actions it receives.

If the platform is told that every button click is a valuable conversion, it may begin optimizing campaigns toward people who click buttons. If duplicate form events inflate one campaign’s performance, more budget may shift toward that campaign.

The platform is responding correctly to incorrect information.

“Google Ads is optimizing toward whatever conversion signals you send it,” our Director of Digital Marketing explains. “So if those signals are incomplete, inflated, or tied to the wrong action, the system is learning from bad inputs.”

That creates several expensive scenarios.

A Strong Campaign Can Look Weak

A campaign may be generating qualified calls or form submissions that the website fails to record.

Because those leads never appear in Google Ads, the campaign seems less effective than it really is. The budget gets reduced or the campaign gets paused.

A Weak Campaign Can Look Strong

Duplicate conversions can make a campaign appear highly productive even when it generates few real leads.

The campaign receives more budget based on results that did not actually happen.

Automated Bidding Can Optimize for the Wrong Behavior

If low-intent events are included as primary conversions, automated bidding may focus on visitors who complete those easy actions.

The system can drive more “conversions” while real lead volume remains flat.

Reported ROI Can Drift Away From Reality

Inflated or incomplete lead counts affect cost per lead, campaign comparisons, forecasts, and client reporting.

The spreadsheet may show improvement while the sales team sees no change.

“That’s how you end up cutting campaigns that are actually producing leads, funding campaigns that aren’t, and reporting ROI that doesn’t match reality.”

What Should You Ask About Your GTM Setup?

You do not need to know how to build every tag to ask better questions about your tracking.

Start with these:

Which website actions are considered primary conversions?
Which events are only being used as supporting engagement signals?
How do we confirm that a form was successfully submitted?
Can one lead trigger more than one conversion?
Are any analytics or advertising tags installed outside GTM?
How are phone calls connected to their original marketing source?
Which conversion actions are currently informing Google Ads bidding?
When was each major form, call, and booking path last tested?
What changed on the website since the last tracking audit?
Who owns the GTM container and its documentation?

The answers should be specific. “We have GTM installed” is not enough.

When Should You Audit Google Tag Manager?

Tracking should be reviewed whenever the systems around it change.

That includes:

Launching a new website or landing page
Replacing or updating forms
Changing call-tracking providers
Introducing a new booking or chat platform
Migrating to a different CMS
Updating a cookie banner or consent platform
Restructuring Google Ads conversion goals
Adding a new CRM or lead-management process
Seeing an unexplained change in lead volume or cost per lead
Finding a large gap between reported conversions and actual leads

Regular maintenance also helps prevent years of outdated tags and inconsistent naming from accumulating inside the container.

GTM supports version histories and Preview mode so changes can be documented and tested before they are published.

What Does a Healthy GTM Setup Look Like?

A healthy GTM setup does not need to track every movement a visitor makes. It needs to capture the actions the business relies on and send them to the right systems accurately.

That usually means:

Business-critical actions are clearly defined
Each lead is counted once
Event names follow a consistent structure
Tags fire only under the intended conditions
Source and campaign details are preserved
GA4 key events reflect meaningful business outcomes
Google Ads bidding uses deliberate conversion signals
Consent settings are configured and tested
Changes are documented
Tracking is retested when the website changes
Website data is regularly compared with real lead records

The goal is not to create more data. It is to create data that helps the team understand where leads come from, what marketing produces them, and where the budget should go next.

As Haller explains:

“They’re not totally without data. They just don’t have the data they need to make good decisions.”

Build a Measurement System You Can Trust

A dashboard is only useful when you know the conversions behind it are being tracked correctly. Google Tag Manager can be installed and active, yet still send incomplete or misleading data to the platforms guiding your marketing decisions.

The only way to know whether it’s working is to test the full path from website action to reported conversion. That means checking what fires, what gets counted, where the data goes, and whether it matches the leads your business actually receives.

At Astute, we audit the full measurement setup across GTM, GA4, Google Ads, call tracking, forms, and lead reporting. We find the gaps, fix the signals, and give your team a clearer view of what’s driving (or dampening) performance.