Verifying Your Tracking Setup with the Tag Assistant

You shipped. Traffic's coming in. But is your tracking actually working?

Most founders don't know. They assume Google Analytics is capturing everything, that Google Search Console is connected, that Tag Manager is firing properly. Then three months later, they realize half their conversions weren't tracked, their traffic data is incomplete, and they've been flying blind the whole time.

Tag Assistant catches these silent failures before they become expensive problems.

This guide walks you through the exact steps to verify your tracking setup using Google Tag Assistant—the browser extension that tells you what's actually firing on your site, not what you think is firing.

Prerequisites: What You Need Before Starting

Before you open Tag Assistant, make sure you have the basics in place:

Access requirements:

• A Google account with admin or editor access to your Google Analytics 4 property
• Admin access to Google Tag Manager (if you're using it)
• Admin or owner access to Google Search Console
• The ability to access your live website from a browser

Technical setup you should have completed:

• A GA4 property created and connected to your website
• Google Tag Manager container installed (if applicable)
• Google Search Console property verified
• Your site live and accessible to the public

What you'll be checking:

• Whether GA4 measurement ID is firing correctly
• Whether GTM container is loading and executing tags
• Whether conversion events are being tracked
• Whether GSC verification is active
• Whether any tracking errors are blocking data collection

If you haven't set up GA4 yet, do that first. If you're tracking referral traffic from AI sources, you'll want to understand how to track ChatGPT 5.5 referrals and other AI citations properly before verifying your setup—this ensures your tracking architecture supports the data you need.

Don't skip this step. A broken tracking setup will give you false confidence in metrics that don't exist.

Step 1: Install Google Tag Assistant

Tag Assistant is a Chrome extension. You need it installed and active before you can verify anything.

Install it here:

Go to the Tag Assistant Chrome extension page and click "Add to Chrome." Confirm the permission request. The extension will appear in your Chrome toolbar.

Why Chrome only?

Tag Assistant is a Chrome extension. If you're using Safari, Firefox, or Edge, you'll need to switch to Chrome for this verification process. Most founders use Chrome for development work anyway, so this shouldn't be a blocker.

Verify the installation:

Click the Tag Assistant icon in your Chrome toolbar. You should see a small popup that says "Tag Assistant is ready." If you see an error or blank popup, uninstall and reinstall the extension.

Don't move forward until you see the "ready" message. A failed installation will give you false negatives on your tracking.

Step 2: Navigate to Your Website and Start a Session

Now open your live website in the same Chrome browser where Tag Assistant is installed.

Use your production domain:

Don't test on localhost or staging. Tag Assistant needs to see your actual live site. Open your main domain (e.g., example.com, not localhost:3000 or staging.example.com).

Click the Tag Assistant icon:

Once your site loads, click the Tag Assistant icon in the Chrome toolbar. A sidebar will open on the right side of your browser.

Start recording:

You'll see a "Start" or "Record" button. Click it. Tag Assistant will now monitor all tags firing on your page in real-time.

Interact with your site:

Navigate through your site as a user would. Click buttons, fill out forms, complete actions you want to track. Tag Assistant is watching and will log every tag that fires.

Record for 30-60 seconds minimum:

Don't just load the homepage and stop. Spend at least 30-60 seconds navigating, clicking, and triggering the events you care about. The more interactions you log, the more complete your verification will be.

If you're testing conversion tracking, actually complete a conversion (or simulate one). If you're testing page view tracking, visit multiple pages. Tag Assistant can only verify what it sees firing.

Step 3: Review the Tag Assistant Summary

After you've recorded your session, stop the recording and review the summary.

Look for the green checkmark:

Tag Assistant will show you a list of tags detected on your site. Tags with green checkmarks are firing correctly. Tags with yellow or red icons have warnings or errors.

Expected tags you should see:

• Google Analytics 4 tag (gtag.js or GA4 measurement ID)
• Google Tag Manager container tag (if you're using GTM)
• Google Ads conversion tags (if you're running ads)
• Any third-party pixels (Facebook, LinkedIn, etc., if applicable)

What you should NOT see:

• Duplicate tags firing multiple times
• Tags with version mismatches
• Deprecated Universal Analytics tags (UA-)

If you see duplicate GA4 tags or both GTM and direct GA4 implementation, you have a problem. Stop here and remove the duplicate. Duplicate tags will inflate your traffic numbers and make your data unreliable.

Step 4: Verify GA4 Is Firing Correctly

GA4 is your primary measurement tool. It needs to be working.

Check the GA4 tag status:

In the Tag Assistant sidebar, find the Google Analytics 4 tag. Click on it to expand the details.

Verify the measurement ID:

You should see a measurement ID that starts with "G-" (e.g., G-XXXXXXXXXX). This ID should match the one in your Google Analytics property settings. If it doesn't match, you're tracking to the wrong property.

To confirm: Log into Google Analytics, go to Admin → Property Settings, and copy your measurement ID. Compare it to what Tag Assistant shows. They must be identical.

Check the tag status:

Tag Assistant will show whether the GA4 tag loaded successfully. You should see:

• "Tag loaded successfully"
• "No errors detected"
• "Event data is being sent"

If you see warnings like "Consent mode not configured" or "User consent not detected," that's not necessarily a failure—it depends on whether your site uses consent mode. But note it for later.

Verify events are firing:

Scroll down in the GA4 tag details. You should see a list of events being captured. At minimum, you should see:

• page_view events (every page you loaded)
• session_start events (when your session began)
• Any custom events you've configured (form submissions, button clicks, etc.)

If you see zero events, GA4 is not tracking. This is a critical failure. Stop and troubleshoot before moving forward.

Step 5: Verify Google Tag Manager Is Firing (If You're Using It)

If you're using Google Tag Manager, you need to verify it's loading and executing tags correctly.

Check the GTM container tag:

In the Tag Assistant sidebar, find the Google Tag Manager tag. It will show your container ID (GTM-XXXXXXX).

Verify the container loaded:

Tag Assistant should show:

• "Container loaded successfully"
• "No errors detected"
• Container ID matches your GTM setup

Check the tags inside the container:

Click on the GTM container to expand it. You should see a list of all tags configured inside that container. This includes:

• GA4 tags
• Conversion tracking tags
• Event tags
• Remarketing tags

Each tag should show whether it fired or not. Tags that fired will have a checkmark. Tags that didn't fire will show a warning or error.

Review tag firing logic:

If a tag didn't fire, check why. Expand the tag details and look for:

• Trigger conditions — Did the trigger fire? (e.g., "Page View trigger" or "Form Submission trigger")
• Tag configuration — Is the tag set up correctly? (e.g., GA4 measurement ID is correct)
• Errors — Does Tag Assistant show any error messages?

If a tag should have fired but didn't, the trigger likely didn't match. For example, if you have a form submission tag that didn't fire, you may not have actually submitted the form during your test, or the form selector in the trigger is wrong.

Test again and actually trigger the action you're trying to track.

Step 6: Check for Conversion Tracking Issues

Conversions are the metrics that matter. If they're not tracking, nothing else matters.

Identify your conversion events:

Before you verify, know what you're trying to track. Common conversions include:

• Form submissions (contact form, signup, demo request)
• Button clicks ("Sign Up," "Start Free Trial," "Download")
• Page visits ("Thank You" page, pricing page, checkout)
• E-commerce transactions (if you're selling)

Trigger each conversion during your test:

During your Tag Assistant recording session, actually complete each conversion action. Fill out and submit forms. Click buttons. Complete purchases. Don't just navigate passively.

Review conversion events in Tag Assistant:

After your session, expand the conversion tracking section in Tag Assistant. You should see each conversion event you triggered listed with a timestamp.

For each conversion:

• Check that the event fired
• Verify the event name is correct (e.g., "form_submit", "purchase", not "undefined")
• Confirm any parameters are being passed correctly (e.g., value, currency, transaction ID)

Look for conversion tag errors:

If a conversion tag has a red or yellow icon, expand it and read the error message. Common issues:

• "Conversion ID not found" — Your conversion ID is wrong or missing. Check your Google Ads account.
• "Tag not firing" — The trigger didn't match. Test the action again and verify the trigger configuration.
• "Invalid parameter" — A required field is missing or formatted incorrectly.

If you see errors, note them. You'll fix them in the next steps.

Step 7: Verify Google Search Console Connection

Google Search Console doesn't fire tags like GA4 does, but you need to verify it's connected and active.

Open Google Search Console:

Go to Google Search Console and log in.

Select your property:

Choose the property that matches your website domain.

Check the verification status:

Go to Settings → Ownership verified. You should see a checkmark and a green "Verified" status. If it says "Verification pending" or "Not verified," your GSC is not properly connected.

Check recent data:

Go to Performance. You should see:

• Impressions (how many times your site appeared in search results)
• Clicks (how many times users clicked to your site from search)
• Average position (where your site ranks on average)

If all these show zero, GSC may not be connected yet (new properties take 24-48 hours to show data). But the property should still be verified.

Verify indexing:

Go to Coverage. This shows which pages Google has indexed. You should see:

• "Valid" pages (indexed and ready to rank)
• "Excluded" pages (not indexed, usually intentional)
• "Error" pages (crawl errors preventing indexing)

If you see a high number of errors, you have indexing problems. This is critical and needs to be fixed before you optimize for rankings. When you're ready to audit your site's indexing and ranking potential, the difference between indexing and ranking explains the priority order.

Step 8: Use Tag Assistant to Review Diagnostic Messages

Tag Assistant provides diagnostic messages that explain what's happening with your tags.

Open the Diagnostics tab:

In the Tag Assistant sidebar, look for a "Diagnostics" or "Messages" tab. Click it.

Read all messages carefully:

Tag Assistant will show you a list of diagnostic messages. These are NOT errors necessarily—they're informational messages that explain what's happening.

Common diagnostic messages:

• "Google Analytics cookie not found" — GA4 hasn't set its cookies yet. This is normal on first visit. Not a problem.
• "Consent mode not configured" — You're not using consent mode to manage user consent. This is fine if you're not collecting personal data or you're complying with consent separately.
• "Tag loaded from Tag Manager" — Your GA4 tag is being loaded through GTM, not directly. This is fine and actually preferred if you're using GTM.
• "Duplicate tag detected" — You have the same tag firing twice. This is a problem. Remove the duplicate.

Act on error messages:

If Tag Assistant shows a red error icon with a message, address it:

• If it's a duplicate tag, remove it from your GTM or your site code.
• If it's a missing ID, find the correct ID and update your tag configuration.
• If it's a trigger issue, test the action again to verify the trigger is correct.

Don't ignore error messages. They're telling you what's broken.

Step 9: Record a Session and Export the Report

Tag Assistant lets you record and save sessions for later review.

Start a fresh recording:

Clear your previous session and start a new recording. This time, go through your entire user journey:

• Land on homepage
• Navigate to key pages
• Fill out and submit a form or complete a conversion
• Check your "Thank You" page or confirmation page

Record for 2-3 minutes to capture a complete user flow.

Stop the recording:

Click "Stop" in the Tag Assistant sidebar.

Export or save the session:

Tag Assistant will show you an option to save or export the session data. Do this. You'll want a record of what was firing for troubleshooting later.

Some versions of Tag Assistant let you export as JSON or CSV. Save this file. If you need to troubleshoot with your developer or a consultant, you can share this report.

Step 10: Cross-Check with GA4 Real-Time View

Tag Assistant tells you what's firing. GA4 Real-Time confirms it's actually being received and processed.

Open Google Analytics:

Log into your GA4 property.

Go to Real-Time:

In the left sidebar, go to Reports → Real-Time.

Trigger an event:

While watching Real-Time, visit your website and trigger an event (page view, form submission, etc.).

Watch for the event to appear:

Within 1-2 seconds, you should see that event appear in the Real-Time view. You should see:

• Your user session
• The page you visited
• The event that fired
• Your location, device, and browser info

If the event appears in Real-Time, GA4 is receiving the data correctly. If nothing appears after 10 seconds, your GA4 tag is not sending data to Google's servers.

Cross-reference with Tag Assistant:

If Tag Assistant says a tag fired but it doesn't appear in Real-Time, you have a connectivity issue. The tag is loading but the data isn't reaching Google. This could be:

• A network firewall blocking Google domains
• A consent mode issue preventing data transmission
• A configuration error in GA4

If both Tag Assistant and Real-Time show the event, you're good. Your tracking is working.

Pro Tips: Common Issues and How to Fix Them

Issue: GA4 Tag Loads But Events Don't Fire

What this means: The GA4 measurement ID is correct and the tag is loading, but you're not seeing any events in Real-Time or in Tag Assistant.

Common causes:

• Your GTM triggers are not configured correctly
• Your GA4 tag is not set up to fire on the right trigger
• You're testing on a localhost or staging domain that GA4 is filtering out

Fix:

1. Verify you're testing on your live production domain
2. In GTM, check your GA4 tag configuration. It should have at least one trigger (usually "All Pages")
3. Make sure the trigger is active and not restricted by URL or other conditions
4. In GA4, go to Admin → Data Streams and confirm your domain is listed
5. Test again

Issue: Duplicate GA4 Tags

What this means: Tag Assistant shows GA4 firing twice. Your traffic numbers are inflated by 2x.

Common causes:

• You installed GA4 both directly on your site AND through GTM
• Your site has GA4 in multiple places (header and footer, or multiple template files)
• You migrated to GTM but forgot to remove the direct GA4 code

Fix:

1. Identify which GA4 implementation is the duplicate
2. Remove one of them (keep the GTM version if you're using GTM; it's easier to manage)
3. Test again with Tag Assistant to confirm only one GA4 tag fires
4. Wait 24 hours for GA4 to stop processing duplicate data

Issue: Conversion Tags Fire But Show Zero Conversions in Google Ads

What this means: Tag Assistant shows your conversion tag firing, but Google Ads shows zero conversions tracked.

Common causes:

• Your conversion ID is wrong
• Your conversion tag is firing on the wrong page
• Google Ads hasn't synced with your website yet (can take 24-48 hours)
• Your conversion is firing but with the wrong value or currency

Fix:

1. In Google Ads, go to Tools → Conversions and copy your exact conversion ID
2. In Tag Assistant, verify this ID matches what's in your conversion tag
3. Verify the conversion tag is firing on the correct page (e.g., thank you page, not checkout page)
4. Wait 24-48 hours for Google Ads to receive and process the data
5. Check Google Ads → Conversions again

Issue: GSC Shows "Verification Pending" or "Not Verified"

What this means: Google Search Console is not verified. Google won't crawl or index your site as effectively.

Common causes:

• You added the property but didn't complete verification
• Your verification method (DNS, HTML file, Google Analytics, Google Tag Manager) is no longer active
• You changed your domain or moved your site

Fix:

1. Go to Google Search Console → Settings → Ownership
2. Choose a verification method (Google Analytics is easiest if you already have it)
3. Complete the verification steps
4. Wait up to 24 hours for verification to complete
5. Check the status again

Step 11: Document Your Findings

Now that you've verified your tracking, document what's working and what's not.

Create a tracking audit checklist:

• GA4 tag is loading and firing correctly
• GA4 measurement ID matches your property
• Events are appearing in GA4 Real-Time
• GTM container is loading (if applicable)
• All GTM tags are firing correctly
• Conversion tags are firing on the right pages
• No duplicate tags detected
• GSC is verified
• GSC is showing indexing data
• No critical errors in Tag Assistant

Mark each item as "Working," "Needs Fix," or "N/A."

If everything is checked as "Working," your tracking setup is solid. If you have "Needs Fix" items, prioritize them by impact:

1. Fix duplicate tags first (they break your data)
2. Fix missing conversion tags (they cost you money)
3. Fix GSC verification (it affects your organic visibility)
4. Fix diagnostic warnings (they may affect data quality)

Step 12: Set Up Ongoing Monitoring

Tracking breaks. New tags get added. Developers make changes. You need to catch problems before they cost you data.

Run Tag Assistant monthly:

Every 30 days, spend 15 minutes running through this verification process again. It takes little time and catches silent failures.

Set up GA4 alerts:

In Google Analytics, go to Admin → Alerts. Create alerts for:

• Sudden drop in traffic (>50% decrease)
• Sudden spike in traffic (>200% increase)
• Zero events for 24 hours
• Zero conversions for 48 hours

These alerts will notify you if something breaks.

Monitor GSC regularly:

Check Google Search Console weekly. Look for:

• New crawl errors
• Sudden drop in impressions
• Pages that were indexed but are now excluded

If you see anomalies, investigate immediately.

Review your tracking after major changes:

If you:

• Update your website (redesign, migration, platform change)
• Add new features or pages
• Change your GTM setup
• Implement new conversion events

...run Tag Assistant again to verify nothing broke.

Troubleshooting: When Tag Assistant Shows Errors

Tag Assistant will sometimes show errors or warnings that aren't immediately clear. Here's how to interpret them:

"Tag loaded but no data sent"

The tag is on your page but it's not communicating with Google's servers. Check:

• Your firewall or network is not blocking Google domains
• Consent mode is not preventing data transmission
• Your GA4 property ID is correct

"Trigger did not fire"

Your GTM trigger is configured but the condition didn't match. Check:

• You actually performed the action the trigger is looking for
• The trigger's conditions (URL, element, event) are correct
• The trigger is not restricted by audience or other filters

"Invalid configuration"

Your tag is set up incorrectly. Check:

• All required fields are filled in
• IDs and credentials are correct
• The tag type matches what you're trying to track

"Consent mode required"

• You're using consent mode but haven't configured it correctly
• Either set up consent mode properly or disable it if you don't need it

If Tag Assistant shows an error and you're not sure how to fix it, take a screenshot and share it with your developer. The error message usually tells you exactly what's wrong.

When to Use Tag Assistant vs. GA4 DebugView

Tag Assistant and GA4 DebugView are complementary tools. Use them together:

Use Tag Assistant to verify:

• Tags are loading on your page
• Tags are firing when they should
• No duplicate tags
• No configuration errors
• GTM is working correctly

Use GA4 DebugView to verify:

• Events are reaching Google's servers
• Events have the correct parameters
• User sessions are being tracked correctly
• Real-time data is flowing into GA4

Run Tag Assistant first. If it shows no errors, then check GA4 DebugView to confirm the data is actually arriving. If Tag Assistant shows errors, fix those first before checking DebugView.

Integration with Your SEO Strategy

Tracking verification isn't just a technical task—it's foundational to your SEO and growth strategy.

When you ship new content, you need to know if it's driving traffic. When you optimize your site, you need to know if it's improving rankings. When you run campaigns, you need to know if they're converting.

All of that depends on accurate tracking.

If you're running a pre-launch SEO push, Karl's pre-launch checklist includes verifying your tracking setup as a critical day-one task. You can't measure what you don't track.

If you've already launched but your organic visibility is low, SEO triage for busy founders prioritizes fixing your tracking alongside your domain audit and keyword roadmap. You need accurate data to know which SEO moves are actually working.

If you're building on a platform like Webflow or Framer, platform-specific SEO issues often break tracking. Webflow SEO settings that move rankings and Framer SEO setup guide both include tracking verification steps because these platforms have specific quirks that affect how tags fire.

Even if you're just doing a day 50 SEO audit, you should re-verify your tracking. Things change. Tags break. New integrations get added. A 15-minute verification session prevents months of bad data.

Key Takeaways

Here's what you need to remember:

Tracking is foundational. Everything else—optimization, strategy, campaigns—is built on the assumption that your tracking works. If it doesn't, you're making decisions based on false data.

Tag Assistant catches silent failures. Most tracking problems don't show obvious errors. Your site looks fine. Your analytics dashboard shows numbers. But the numbers are wrong. Tag Assistant shows you what's actually firing.

Verification takes 15 minutes. Download the extension, navigate your site, review the results. That's it. Fifteen minutes of work prevents months of bad decisions.

Fix errors immediately. Duplicate tags, missing conversions, verification issues—don't wait. Fix them the day you find them. The longer they persist, the more bad data you collect.

Monitor ongoing. Run Tag Assistant monthly. Set up GA4 alerts. Check GSC weekly. Tracking breaks when you're not looking. Catch problems early.

Document your setup. Save your Tag Assistant reports. Keep notes on what's working. When you hire a developer or consultant, you have a baseline to work from.

You shipped. Now make sure you can measure what you shipped. Tag Assistant is your verification tool. Use it.

Next Steps

Now that your tracking is verified:

1. If you haven't done a domain audit yet, the 5 pillars of modern SEO breaks down the full picture—crawl, content, links, intent, and AEO. Your tracking setup is the foundation for measuring all of these.

2. If you're seeing tracking data but low traffic, SEO basics: 12 concepts a busy founder can't skip walks through the fundamentals. You might be tracking correctly but optimizing wrong.

3. If you're confused by SEO terminology, the busy founder's glossary decodes 50+ terms agencies use. Understanding the language helps you understand the strategy.

4. If you're tracking AI-driven traffic, tracking ChatGPT 5.5 referrals shows you how to set up UTMs and GA4 to capture citations and referrals from AI models. This is increasingly important as AI becomes a traffic source.

Your tracking is verified. Your data is clean. Now build on it.