General Guide: See Global Events Not Firing Guide for universal concepts.
Quick Diagnosis
1. Check Tag Installation
Verify your tracking code is properly installed:
- View page source and search for tracking ID
- Use browser developer tools Network tab
- Check for JavaScript errors in Console
2. Browser Extensions
Common blockers:
- Ad blockers (uBlock Origin, AdBlock)
- Privacy extensions (Privacy Badger, Ghostery)
- Brave browser shields
Test in incognito mode without extensions.
3. Consent Management
If using cookie consent:
- Verify consent is granted before tags fire
- Check consent mode implementation
- Test with consent granted
TinaCMS-Specific Issues
Headless Architecture
TinaCMS is a headless CMS — it does not serve HTML or restrict JavaScript. Tracking issues are in your frontend framework, not TinaCMS itself.
Common headless CMS tracking problems:
- SPA route changes not tracked — Single-page apps (React, Vue, Next.js) don't trigger full page loads on navigation. You must fire
page_viewevents manually on route changes or use GTM's History Change trigger. - SSR hydration timing — If using server-side rendering (Next.js, Nuxt), tracking scripts may fire before React hydrates. Place gtag/pixel initialization in a
useEffecthook oronMountedlifecycle. - Build-time vs. runtime — Static site generators (Gatsby, Astro) pre-render pages at build time. Ensure tracking scripts are client-side only, not executed during the build.
Framework-Specific Fixes
React / Next.js:
// Use next/script or useEffect for client-side only
import Script from 'next/script';
// or in _app.js useEffect to fire page_view on route change
Vue / Nuxt:
// Use vue-gtag plugin or nuxt-gtag module for automatic route tracking
Gatsby:
// Use gatsby-plugin-google-gtag for automatic page tracking on route changes
Debugging Tools
Google Tag Assistant
- Install Tag Assistant
- Start recording
- Navigate your site
- Review tag status and errors
Meta Pixel Helper
- Install the Chrome extension
- Visit your site
- Check for pixel status and events
Browser Developer Tools
- Open Console tab for errors
- Check Network tab for tracking requests
- Search for your tracking ID
Verification Steps
- Clear cache and cookies
- Test in multiple browsers
- Check from different networks
- Verify in analytics platform real-time reports