Skip to main content

How to Verify Your Conversion Tracking Is Firing

If you're running Google Ads or Meta (Facebook) ads and using TrackStat online scheduling links, you've likely added tracking scripts to TrackStat so you can measure how many patients book through your ads. This article walks you through how to confirm those scripts are actually firing — without needing your ad agency or a developer.


Before You Start: What TrackStat Does (and Doesn't) Handle

TrackStat is responsible for:

  • Running the scripts you paste into your settings on the booking and thank-you pages

Outside of TrackStat's scope:

  • Writing or fixing your scripts

  • Confirming conversions appear inside your Google Ads or Meta Ads Manager account

  • Your website setup or Google Tag Manager configuration

If your script fires correctly from TrackStat's side, our job is done. If something isn't showing up in your ad account after that, your ad agency or website team will need to investigate on their end.


Two Key Terms to Know

Both Google and Meta tracking work in two parts:

Part

What it does

Where it goes

Global Site Tag (Google) / Base Pixel (Meta)

Loads the tracking — like turning the engine on

Every page

Event Snippet (Google) / Event Code (Meta)

Records the conversion — like pressing the gas

Thank You page only (shown after booking)

The Event Snippet / Event Code only works if the first script loaded first. If the engine isn't on, pressing the gas does nothing.


Getting Set Up: Use Chrome Incognito

⚠️ Important: Always test in a Chrome Incognito window with browser extensions turned off. Ad blockers and privacy extensions can block Google and Meta tracking, which gives you a false "not working" result.

How to open Incognito with extensions off:

  1. Open Google Chrome

  2. Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) to open an Incognito window

  3. In Incognito, extensions are off by default — you're good to go


Testing Google Conversion Tracking

Step 1 — Open your booking link

In your Incognito window, paste your new patient online scheduling link and load the page.

Step 2 — Open Developer Tools and check for the Global Site Tag

  1. Press F12 on your keyboard (or right-click the page and select Inspect)

  2. A panel opens at the bottom or side of your screen. Click the Network tab at the top of that panel

    • If you don't see it, click the » arrows to find it in the dropdown

  3. In the filter/search box, type: gtag

  4. Press F5 to reload the page

✅ You should see a line appear starting with js?id=... — this means the Global Site Tag loaded successfully.

Step 3 — Book a test appointment

Go through the booking flow and complete a test appointment. You'll land on the Thank You / confirmation page.

Step 4 — Check that the conversion fired

Still on the Thank You page, in the same Network tab:

  1. Clear the filter box and type: conversion

    • If nothing appears, also try: pagead

  2. Look at the Status column next to any lines that appear

Step 5 — Check the Console for errors

  1. Click the Console tab (next to the Network tab)

  2. Look for any red error text — specifically: gtag is not defined

How to Read Your Result

What you see

What it means

Result

A conversion or pagead line with status 200, 204, or 302 — and no red gtag is not defined error

Your conversion tracking is firing

✅ Pass

Red gtag is not defined error in the Console, and the conversion line shows (failed) or doesn't appear

The conversion is not firing — your script setup has an issue

❌ Fail

No gtag/js line appeared at all in Step 2

Nothing was pasted, or it's in the wrong field

❌ Fail

If you got a Fail result, double-check that you were in Incognito with extensions off before drawing conclusions — ad blockers are the most common cause of false failures.


What to Do If It Failed

If you see a gtag is not defined error:

This usually means the Global Site Tag field contains a Google Tag Manager container script instead of a Google Ads Global Site Tag. The Event Snippet needs the gtag.js version of the Global Site Tag to work.

Your ad agency or website team will need to either:

  • Paste the correct Google Ads Global Site Tag (the gtag.js version) into the Global Site Tag field in TrackStat, or

  • Set up the conversions entirely inside Google Tag Manager and remove the Event Snippets

The TrackStat settings screen shows exactly which script goes in which field — share that with them as a reference.

If nothing was detected at all:

Make sure the Global Site Tag is pasted in the Global Site Tag field and the Event Snippet is pasted in the Event Snippet (Thank You Page) field in your TrackStat settings. Once updated, run through the test steps again.


Testing Meta (Facebook) Pixel Tracking

Meta Pixel tracking works exactly the same way as Google — just with different names and different things to look for.

Google

Meta equivalent

Global Site Tag

Base Pixel code (fbq('init', …))

Event Snippet

Event code (fbq('track', 'Lead') etc.)

Network filter: gtag

Network filter: fbevents

Network filter: conversion / pagead

Network filter: tr? or facebook

Error: gtag is not defined

Error: fbq is not defined

⚠️ Ad blockers block Meta even more aggressively than Google. Incognito with extensions off is especially important here.

Step 1 — Open your booking link

In your Incognito window, open your new patient online scheduling link.

Step 2 — Check for the Base Pixel

  1. Press F12 → click the Network tab

  2. Type fbevents in the filter box

  3. Reload the page (F5)

✅ You should see a line for fbevents.js — that's the Base Pixel loading.

Step 3 — Book a test appointment

Go through the booking flow and complete a test appointment. You'll land on the Thank You page.

Step 4 — Check that the conversion fired

  1. In the Network tab, clear the filter and type tr? (or facebook)

  2. Check the Status column of any lines that appear

Step 5 — Check the Console for errors

Click the Console tab and look for red errors — specifically: fbq is not defined

How to Read Your Result (Meta)

What you see

What it means

Result

A facebook.com/tr/?… line with status 200 — and no red fbq is not defined error

Your Meta Pixel is firing

✅ Pass

Red fbq is not defined error, and the tr? line shows (failed) or is missing

The pixel is not firing — your script setup has an issue

❌ Fail

No fbevents.js line appeared at all in Step 2

Nothing was pasted, or it's in the wrong field

❌ Fail

💡 Tip: The free Meta Pixel Helper Chrome extension gives you a quick badge showing which pixel and events fired. You can install it and use it in a normal browser window (just make sure ad blockers are off) as a quick second check.


Frequently Asked Questions

The script fired from TrackStat, but I don't see the conversion in my Google Ads / Meta Ads Manager account. Is something wrong?

Not necessarily — this is expected. TrackStat confirms the script fired from our pages. Whether it registers inside your ad account depends on your account setup and can take several hours to appear. Your ad agency is the right contact for anything on that side.

How do I know if my script is a Google script or a Meta script?

  • Google scripts mention gtag, googletagmanager.com, or IDs starting with AW-, G-, or GTM-

  • Meta scripts mention fbq, fbevents.js, or connect.facebook.net

Use the matching section above to test the right one.

What's the difference between AW-, G-, and GTM- IDs? (Google)

  • AW- = Google Ads conversion tracking (this is typically what you want)

  • G- = Google Analytics (a different product)

  • GTM- = Google Tag Manager container (this goes in Tag Manager, not in TrackStat's script fields directly)

If you're unsure which you have, share this with your ad agency — they'll know what to do.

I followed all the steps and it's still not working. What now?

Reach out to TrackStat support. Share what you saw in the Network tab and Console so we can help diagnose the issue quickly.

Did this answer your question?