Analytics

How to verify your tracking is actually working

TS Talha Shahzad··5 min read
The short version
  • Most analytics setups are never tested before launch, leading to hidden data gaps or duplicate triggers.
  • The GA4 DebugView is the most reliable tool to isolate and verify test events in real time without polluting reports.
  • Google Tag Assistant provides visual confirmation of container loads and tag firing sequences.
  • Always perform end-to-end sandbox purchases or form bookings to ensure transaction metadata is captured correctly.

If you have just finished setting up a new Google Analytics container, you should be asking: how do I know if my analytics tracking is set up right? Too many agencies and founders complete their tracking configurations, publish the changes, and simply hope the data rolls in correctly.

This is the technical equivalent of writing software code and pushing it to production without compiling it. More than half of the analytics configurations I audit are broken. They suffer from duplicate tracking tags, missing purchase parameters, or conversion tags that fire on simple button clicks instead of successful submissions.

You cannot manage a business on guess-work. You need a structured, repeatable way to verify that your tracking tags are working exactly as intended before you rely on them.

Google Tag Assistant: the timeline check

The first tool in your validation toolkit is Google Tag Assistant (formerly GTM Preview Mode). It provides a visual, step-by-step timeline of every event that occurs on your page and shows which tags fired at each millisecond.

To start a verification session:

  1. Open Google Tag Manager.
  2. Click the Preview button in the top-right corner.
  3. Enter your website URL and click Connect.
  4. This opens your site in a new browser window with a "Debugger Connected" badge in the bottom-right corner.

On the left side of your Tag Assistant screen, you will see a list of timeline events (such as Consent Initialization, Container Loaded, DOM Ready, and Window Loaded). Clicking on any of these events reveals which tags fired at that moment.

If you are checking a standard GA4 page_view tag, click on Container Loaded. You should see your GA4 Configuration tag listed under Tags Fired. If it is under Tags Not Fired, your GTM trigger is set up incorrectly or the container code is missing from the page source.

The GA4 DebugView: real-time event stream

While Tag Assistant shows you what Google Tag Manager is doing, the GA4 DebugView shows you what Google Analytics is actually receiving.

Do not rely on the standard GA4 Realtime report to test new tracking. The Realtime report aggregates data across all active visitors and has a natural delay of several minutes. If you have active traffic on your site, your own test visits will get lost in the noise.

DebugView isolates your specific device using a debug parameter sent by GTM preview mode. It displays your actions in a linear, second-by-second timeline.

To use it:

  1. Keep your Tag Assistant preview window open.
  2. In GA4, go to Admin, navigate to Data Display, and click DebugView.
  3. Go back to your website preview window and click a link or scroll down.
  4. Return to GA4. Within ten seconds, you should see those actions appear as circular event nodes in the DebugView timeline.

Click on any event (such as page_view or click) to inspect the parameters. If you have custom parameters configured, expand the parameters folder to verify that they are receiving the correct text values.

Want a website that turns visitors into customers, not just compliments?

Book a 15-min intro

End-to-end form and booking verification

Testing that a tag fires is not the same as testing that it fires correctly. You must test your conversion paths under different scenarios to rule out false positives.

For form submissions:

  • The Failure Test: Go to your form, leave the required fields blank, and click the submit button. Check Tag Assistant. Did your conversion tag fire? If it did, your trigger is set to fire on click rather than successful submission. You are recording conversions for users who failed to fill out the form.
  • The Success Test: Fill out the form correctly and submit it. The tag should fire exactly once. Verify in DebugView that the event (e.g., generate_lead) arrived with the correct form name parameter.

For booking tools:

  • If you use an embedded scheduler like Calendly, complete a full test booking.
  • Confirm that the confirmation screen triggers the conversion event.
  • Check that the event does not fire again if you refresh the confirmation page.

Testing e-commerce purchases safely

E-commerce purchases are the most critical events to verify because they pass financial data. A single typo in your dataLayer variables can result in GA4 reporting zero revenue or double-counting transactions.

If your payment processor (like Stripe) is in test mode, you can use a test credit card to complete a checkout.

Watch GTM and DebugView for the purchase event:

  • Check the Items Array: GA4 expects a specific structure for products (item_id, item_name, price, quantity). Expand the items variable in DebugView to confirm that every product in the cart is listed with its correct metadata.
  • Check the Transaction Value: Verify that the total revenue parameter matches the checkout value.
  • Check Currency: Ensure the currency parameter matches your store's configuration (e.g., USD, CAD).

If you must test on a live production environment, make a real purchase using your own card, verify the tags fire, and then immediately refund the transaction in your store backend. The refund will not erase the test data from your historical reports instantly, but it ensures your accounting remains clean.

Hunting down duplicate tags

Duplicate tracking is the most common cause of inflated conversion rates. If your Facebook pixel or GA4 configuration fires twice on a single page load, you will report double the conversions you actually earned.

Look out for these common duplication sources:

  1. Multiple GTM Containers: Check your page source code. If GTM is installed twice (for example, once via a Shopify app and once hardcoded in the theme), every event will trigger double tags.
  2. Hybrid Setup Collisions: Ensure you do not have a hardcoded tag (like an old analytics.js script) running on the same page as a GTM tag doing the same job.
  3. CMS Platform Integrations: Many platforms like Webflow or WordPress have native integration fields where you enter your GA4 ID. If you enter your ID there and also load a GTM container that triggers the same ID, they will conflict. Pick one method (preferably GTM) and disable the other.

Clean tracking is not a luxury; it is the prerequisite for scaling. If you are struggling with missing events, or if your DebugView is failing to show your test clicks, a professional tracking audit and validation project can trace the errors. Verify the data loop from the browser to the server before you make your next strategic move.

Prefer to hire through Upwork?
Top Rated Plus, 100% Job Success, 450+ projects shipped. See the reviews and start a contract.
Hire me on Upwork

FAQ

How do I know if my analytics tracking is set up right?

You must test the site using Google Tag Assistant in preview mode and watch the events populate in the GA4 DebugView. If your custom events (like signups or purchases) appear with the correct parameters, your tracking is configured properly.

Why is my GA4 DebugView not showing any events?

This is usually caused by ad blockers, strict browser privacy settings, missing developer filters, or delayed container publishing. Ensure all blockers are disabled and that your browser is using the preview mode cookie.

Should I test conversions using live production transactions?

If possible, use staging environments or sandboxed test modes (like Stripe test cards) to complete transactions. If you must test on production, make a real purchase and then immediately refund it, verifying that the transaction ID and revenue show in DebugView.

All posts
the next step is small

Want a site that does this for you?

15 minutes, no deck, no pressure. Worst case, you leave with a free plan.

keep reading

More notes