You spent months setting up GA4. You configured events, built audiences, connected Google Ads. But here's the question nobody asks until it's too late: is any of it actually working?
Broken analytics is invisible. You don't get error messages when your consent mode blocks all tracking. You don't get alerts when your GTM container fires tags into the void. You just get bad data — and you make decisions based on it.
That's why we built the OPIN Analytics Audit Tool — a free, no-signup scanner that checks your GA4 and GTM implementation in seconds. Enter a URL, get a detailed report. No sales pitch, no email gate.
What the Free GA4 & GTM Audit Tool Does
The tool scans any publicly accessible URL and evaluates your analytics implementation across multiple dimensions. It's not a surface-level check — it inspects the actual tag firing behavior, container configurations, and compliance signals on the page.
Here's what gets checked:
- GA4 Detection: Confirms whether a GA4 property is firing on the page, identifies the Measurement ID, and checks if the data stream is actually receiving hits.
- GTM Container Analysis: Detects Google Tag Manager containers, checks for proper installation (both
<script>and<noscript>fallback), and identifies container IDs. - Consent Mode v2: Checks whether Google Consent Mode v2 is implemented — a requirement for any site serving EU users or running Google Ads in the EEA since March 2024.
- Server-Side Tracking Signals: Looks for indicators of server-side GTM or server-side tag deployment, which significantly improves data accuracy and reduces ad blocker data loss.
- Meta Conversions API (CAPI): Detects whether Meta's Conversions API is implemented alongside the Meta Pixel — critical for Facebook/Instagram ad attribution.
- KPI Event Tracking: Identifies whether key business events (purchases, leads, signups) are being tracked beyond basic pageviews.
- Legacy Universal Analytics: Flags if the deprecated UA tracking code is still present, which has been collecting no data since July 2023.
Why Auditing Your GA4 Setup Matters
The cost of broken analytics isn't theoretical. It's measured in wasted ad spend, missed conversions, and strategic decisions built on lies.
Broken Tracking = Wasted Ad Spend
If your GA4 conversion events aren't firing correctly, Google Ads can't optimize your campaigns. Smart Bidding relies on conversion signals. Feed it garbage, and it optimizes for garbage. We've seen companies burning $15,000–$50,000/month on Google Ads with GA4 conversion tracking that was silently broken for weeks.
Consent Mode Gaps = Legal Exposure
Since March 2024, Google requires Consent Mode v2 for any advertiser targeting EEA users. India's Digital Personal Data Protection Act (DPDP Act, 2023) adds another layer — websites collecting data from Indian users need demonstrable consent mechanisms. If your consent implementation is misconfigured, you're collecting data you shouldn't be, or worse, not collecting data you legally could.
Missing Server-Side Tracking = 20-35% Data Loss
Browser-based tracking loses between 20% and 35% of events to ad blockers, ITP (Safari's Intelligent Tracking Prevention), and browser privacy features. Server-side tracking recovers most of this. If you're running significant paid media and don't have server-side tracking, your attribution data is substantially incomplete.
Orphaned UA Code = Technical Debt
Universal Analytics stopped processing data on July 1, 2023. But we still find analytics.js and gtag('config', 'UA-XXXXXX') on roughly 40% of sites we audit. This dead code adds page weight, creates console errors, and occasionally conflicts with GA4 tags.
How the Audit Scoring Works: A-F Grading
After scanning your site, the tool assigns a letter grade from A to F based on a weighted scoring system. Here's what each grade means:
| Grade | Score Range | What It Means |
|---|---|---|
| A | 90–100 | Excellent implementation. GA4 active, consent mode configured, server-side tracking detected, key events firing. Production-ready. |
| B | 75–89 | Solid foundation with minor gaps. Typically missing server-side tracking or advanced consent configuration. |
| C | 60–74 | Functional but with significant blind spots. Usually missing consent mode or relying entirely on client-side tracking. |
| D | 40–59 | Serious issues. GA4 may be partially configured, but critical components are missing or broken. |
| F | 0–39 | Fundamentally broken or absent. No GA4 detected, or implementation has critical failures. |
The scoring weights prioritize what actually impacts business decisions: GA4 presence and event tracking carry the most weight, followed by consent compliance, then advanced features like server-side tracking and CAPI.
The 7 Most Common Issues We Find
After running thousands of audits, clear patterns emerge. These are the issues that show up most frequently — and they're almost always fixable within a day or two.
1. Missing Consent Mode v2 Implementation
Found on approximately 65% of audited sites. The site either has no consent management platform (CMP), or the CMP isn't properly integrated with Google's consent signals. This means ad_storage, analytics_storage, and ad_personalization consent types aren't being communicated to Google tags.
2. No Server-Side Tracking
About 80% of sites rely entirely on client-side tag firing. For small informational sites, this might be acceptable. For any site spending more than $5,000/month on paid media, the data loss is material enough to distort campaign optimization.
3. Legacy UA Code Still Active
Roughly 40% of sites still load Universal Analytics scripts. These generate unnecessary network requests, add 15-30KB of dead JavaScript, and occasionally cause tag sequencing issues in GTM.
4. Missing GTM Noscript Fallback
The <noscript> iframe for GTM should be placed immediately after the opening <body> tag. About 30% of sites either omit it entirely or place it in the wrong location. While this primarily affects users with JavaScript disabled (a small percentage), it also impacts certain bot and crawler scenarios.
5. No Custom Event Tracking
GA4 tracks pageviews by default, but pageviews alone tell you almost nothing about business performance. Roughly 50% of sites we audit have no custom events configured — no form submissions, no button clicks, no scroll tracking, no video engagement. They're flying blind.
6. Multiple GA4 Properties Firing Simultaneously
About 15% of sites fire two or more GA4 Measurement IDs on the same page — typically a leftover from migration or agency transitions. This inflates session counts, creates duplicate events, and makes reporting unreliable.
7. Consent Mode Without a CMP
Some implementations set consent mode defaults in GTM but never actually deploy a cookie consent banner. The result: consent signals are permanently set to "denied," and the site collects zero analytics data from EU/EEA visitors. It's compliance theater that actively harms data collection.
Step-by-Step: How to Use the Free Audit Tool
The process takes under 60 seconds. No account creation, no email required.
- Go to the tool: Open opinsolutions.com/tools/analytics-audit in your browser.
- Enter your URL: Type or paste the full URL of the page you want to audit (e.g.,
https://yoursite.com). The tool scans the specific page you enter, so test your homepage and key landing pages separately. - Click "Run Audit": The scanner will analyze the page's tag implementation, consent signals, and tracking configuration.
- Review your report: You'll get a letter grade (A–F) along with a detailed breakdown of each check. Green checks indicate passing items; red flags indicate issues that need attention.
- Prioritize fixes: Start with red-flagged items. The report explains what each issue means and why it matters, so you can brief your developer or agency with specific action items.
- Re-scan after fixes: Once changes are deployed, run the audit again to verify the fixes landed correctly. Tag changes are notoriously fragile — always verify.
What to Do After Your Audit
An audit score is a starting point, not a destination. Here's how to act on your results:
If You Scored A or B
Your implementation is solid. Focus on ongoing monitoring — set up GA4 anomaly alerts, schedule quarterly audits, and consider advanced optimizations like enhanced conversions or offline conversion imports. If you're not already using server-side tracking, that's the biggest remaining uplift.
If You Scored C
You have a functional foundation but meaningful gaps. Prioritize consent mode implementation (if missing) and custom event tracking. These two changes alone typically move a C to a B. Consider a professional analytics audit to identify configuration issues the automated tool can't catch.
If You Scored D or F
Your analytics data is unreliable and likely misleading your business decisions. Stop making data-driven decisions based on this data — it's worse than making decisions with no data, because it creates false confidence. Get the fundamentals fixed first: proper GA4 installation, correct GTM setup, and basic event tracking.
For companies in India, ensure your implementation accounts for DPDP Act requirements. Our DPDP Readiness Score tool can help you evaluate your compliance posture alongside your analytics setup.
Need Professional Help?
The audit tool identifies problems. Fixing them — especially consent mode integration, server-side tracking setup, and custom event architecture — often requires hands-on implementation work. Talk to our team if you need implementation support. We handle GA4, GTM, server-side tracking, and consent management for companies across India and internationally.
You can also start with our comprehensive free audit request, where our team manually reviews your full analytics setup and provides a detailed remediation plan.
Why We Built This Tool
Most analytics audits are locked behind sales calls and SOWs. You shouldn't need to talk to a salesperson to find out if your GA4 is broken. We built the OPIN Analytics Audit Tool because the analytics industry has a transparency problem — agencies profit from keeping you confused about what's working and what isn't.
This tool gives you a clear, honest assessment in seconds. If everything looks good, great — you don't need us. If things are broken, at least you know what to fix and can make an informed decision about whether to handle it in-house or bring in help.
Frequently Asked Questions
Is the GA4 audit tool really free?
Yes. No signup, no email gate, no credit card. Enter a URL, get your report. We built it as a public utility for the marketing community. There's no catch — if your setup is clean, you'll know in seconds and never hear from us.
What's the difference between this tool and Google's Tag Assistant?
Google Tag Assistant is a browser extension that shows you what tags are firing on a page. It's useful for debugging, but it doesn't evaluate your implementation against best practices. Our tool goes beyond detection — it assesses whether your setup includes consent mode, server-side tracking, proper GTM installation, and business-critical event tracking, then grades the overall health of your implementation.
Does the tool work on single-page applications (SPAs)?
The tool scans the initial page load, which captures most tag firing behavior. For SPAs built with React, Next.js, or Angular, the initial load typically includes all GTM and GA4 initialization code. However, route-change event tracking within SPAs requires manual testing. If your SPA relies heavily on virtual pageviews, we recommend supplementing the automated audit with manual validation in GA4's DebugView.
How often should I audit my GA4 and GTM setup?
At minimum, quarterly. But you should also run an audit after any website redesign, CMS migration, tag manager change, or consent platform update. These are the events that most commonly break tracking. For high-traffic e-commerce sites spending significant amounts on paid media, monthly audits are worth the five minutes they take.
Can the tool detect issues with GA4 event tracking accuracy?
The tool detects whether GA4 is present and firing, and whether custom events are configured. It cannot validate the accuracy of event parameters (e.g., whether your purchase event sends the correct revenue value) because that requires access to your GA4 property data. For deep event validation, you need either GA4's DebugView or a professional implementation audit.