If you’ve taken over an existing website or just installed MonsterInsights and can’t find the Google Analytics code in the WordPress theme editor, you’re not missing it; it isn’t there. MonsterInsights injects the tracking code dynamically at page load rather than hardcoding it into your theme files. This means the tag fires correctly without you ever seeing it in the editor.
This guide shows you two quick ways to confirm your tracking tag is working: Omnibug (the easiest method) and Chrome DevTools (a more hands-on alternative). Either one will give you a definitive answer in under a minute.
Why You Can’t Find the Code in Your Theme Editor
Traditional Google Analytics setup required you to paste a snippet of JavaScript directly into your theme’s header.php file. MonsterInsights takes a different approach: it outputs the tracking code automatically through WordPress’s built-in script loading system. The tag is real and active; it’s just managed by the plugin rather than sitting in a file you can open and read.
Checking your theme files or the WordPress customizer for the GA code will always come up empty when MonsterInsights is handling the integration. The checks below are the right way to confirm everything is working.
Method 1: Omnibug (Recommended)
Omnibug is a free browser extension that intercepts and decodes outgoing analytics and marketing tag requests, displaying them in a readable format inside Chrome DevTools.
Step 1: Install Omnibug
- Open Chrome and search for Omnibug in the Chrome Web Store, or find it directly by searching “Omnibug Chrome extension”.
- Click Add to Chrome, then click Add extension in the confirmation prompt.
Step 2: Open Omnibug on Your Site
- In Chrome, navigate to your website.
- Right-click anywhere on the page and select Inspect, or press Cmd + Option + I on Mac / Ctrl + Shift + I on Windows.
- In the DevTools panel, click the Omnibug tab. If you don’t see it, click the » arrow at the end of the tab bar to find it.
- Reload the page with Cmd + R (Mac) or Ctrl + R (Windows) so Omnibug can capture the requests made during load.
Step 3: Check for Your Google Analytics Tag
Omnibug will list every analytics request it detects. Look for an entry labeled Google Analytics 4 or showing a URL that includes google-analytics.com.
- If a GA4 entry appears: your tracking code is firing. Click the row to expand it and see the full details, including your Measurement ID (starting with G-) and the event data being sent.
- If no GA4 entry appears: the tag is not firing on this page. See the troubleshooting section at the end of this guide.
Navigate to other pages on your site while Omnibug is open and it will capture requests for each new page you load.
Method 2: Chrome DevTools Network Tab
If you prefer not to install an extension, you can use Chrome’s built-in developer tools to see the network requests your page makes; including the request to Google Analytics.
Step 1: Open DevTools
- Navigate to your website in Chrome.
- Right-click anywhere on the page and select Inspect, or press Cmd + Option + I on Mac / Ctrl + Shift + I on Windows.
- Click the Network tab at the top of the DevTools panel.
Step 2: Reload the Page
With the Network tab open, press Cmd + R (Mac) or Ctrl + R (Windows) to reload the page. DevTools will capture every network request made during the load.
Step 3: Filter for Google Analytics Requests
- In the filter bar near the top of the Network tab, type collect or google-analytics.
- Look through the results for a request to a URL that includes google-analytics.com or analytics.google.com.
- If you see a request to https://www.google-analytics.com/g/collect: this is GA4 sending data to Google. Your tag is firing. Click on the request and open the Payload tab to see the exact data being sent, including your Measurement ID (it starts with G-).
- If no matching requests appear: the tag is not firing. See the troubleshooting section below.
Troubleshooting: Tag Not Detected
If neither method finds a Google Analytics tag on your site, work through the following checks:
Confirm the tag isn’t excluded for logged-in users. MonsterInsights has an option to skip tracking for logged-in administrators and editors. If you’re checking while logged in to WordPress, the tag may intentionally not fire. Log out or open your site in an incognito window to test as a regular visitor.
Check that MonsterInsights is connected to a GA4 property. In your WordPress dashboard, go to Insights → Settings → General. Under the Authentication section, you should see your connected Google Analytics property listed. If the status shows disconnected or the field is empty, click Connect MonsterInsights and follow the setup steps.
Check that the plugin is active. Go to Plugins → Installed Plugins and confirm MonsterInsights is both installed and activated. A deactivated plugin will not inject any tracking code.
Disable any ad blockers or privacy extensions while testing. Browser extensions that block trackers will also block the GA tag from loading during your test. Temporarily disable them and reload the page before running the check again.
Check whether caching is interfering. If you’re using a caching plugin (such as WP Rocket or W3 Total Cache), clear the cache and reload the page, then run the check again. Stale cached pages can sometimes prevent dynamically injected scripts from appearing.
Frequently Asked Questions
Why can’t I see the Google Analytics code in my theme’s header.php file?
MonsterInsights manages the tracking code through WordPress’s script queue rather than inserting it directly into theme files. This is a deliberate design choice — it means the tag stays in place even if you switch themes, and it allows the plugin to control when and how the tag loads. The code is present on your live pages; it’s just not stored in a file you can browse to in the editor.
What Measurement ID should I be looking for?
Your GA4 Measurement ID starts with G- followed by a string of letters and numbers (for example, G-ABC123XYZ). You can find it in Google Analytics under Admin → Data Streams → [your stream] → Measurement ID. When using Chrome DevTools, you can confirm MonsterInsights is sending data to the right property by checking that this ID appears in the network request payload.
Omnibug shows the tag but Google Analytics reports show no data. What’s wrong?
There can be a delay of up to 24–48 hours before data appears in standard Google Analytics reports. For real-time confirmation, go to Reports → Realtime in Google Analytics while your site is open in another tab. You should see your own visit appear within a few seconds of loading a page. If the real-time report remains at zero, double-check that you’re looking at the correct GA4 property.
Does this work the same way for MonsterInsights Lite and Pro?
Yes. Both the free (Lite) and paid (Plus/Pro) versions of MonsterInsights inject the GA4 tracking code dynamically in the same way. The verification steps above apply to all versions of the plugin.
