Understanding your audit score

How the score is calculated

The score is calculated from the checks available to your plan and property configuration. Each check has a severity weight: critical checks are worth more than low-severity checks. A check that passes contributes its full weight to the score; a check that fails contributes zero. Skipped checks (due to missing data or unavailable features) are excluded from the denominator and do not penalise your score.

The module scores are calculated independently first. The overall score is then a weighted average of module scores, with higher-priority modules (P0) weighted more heavily than P1 and P2 modules. This means a critical failure in your tag setup will drag the overall score down more than a low-severity data quality issue.

Letter grades explained

The letter grade is derived from your numeric score:

C vs D: what's the practical difference?

A C score (60–69) typically means your GA4 property is collecting data and broadly working, but has identifiable problems — perhaps consent mode is misconfigured, UTM parameters are inconsistently formatted, or data retention is set too low. The data is usable but may be skewed.

A D score (50–59) signals that critical checks have failed. At this level, you should expect issues like duplicate events inflating key metrics, missing consent gating causing legal exposure, or a broken funnel in your e-commerce tracking. Decisions based on this data carry real risk.

Score changes between audits

GA4 Audits tracks your score over time. A sudden drop between two audits almost always reflects a real change — a new tracking deployment, a CMP update, or a GA4 configuration change. Use the Compare tab on the audit page to diff two audit results side-by-side and pinpoint which checks changed status.