Where to find it
Open a project's scan to see the Privacy Score KPI tile at the top of the view, displayed as a number with the subtitle "out of 100". Next to it sits the Status tile, which shows the matching compliance tier as a colored badge, and a Findings tile counting the issues detected.
The score is a single headline number, but it is backed by a score ring, a detected-technologies list, and a findings breakdown lower on the page, so you can always trace why it landed where it did.
What the score measures
The Privacy Score combines six weighted checks: whether a consent management platform is present, whether the CMP loads at the right time, whether Google Consent Mode is in place, whether tracking fires before consent, whether privacy policy links are present, and whether any consent violations occurred. Each check contributes a portion of a raw total, and that total is normalized onto a 0 to 100 scale so the tile always reads out of 100.
Because the score is normalized, you should read it as a percentage of the maximum achievable compliance posture, not as a raw point count. A perfectly configured site approaches 100, while a site with pre-consent leaks and no CMP lands low.
Reading the compliance tier
The score maps to one of three tiers. A score of 80 or above is Compliant and shows a green badge. A score from 50 to 79 is At Risk and shows a yellow badge. A score below 50 is Non-Compliant and shows a red badge. If a project has never been scanned, the status reads Not Scanned.
The tier is what most stakeholders react to first, so use it as the quick read and the numeric score as the detail. Moving up a tier usually means resolving the highest-weight findings, such as eliminating pre-consent tracking or adding a properly timed CMP.
Using the breakdown and findings
Below the KPI tiles, the score ring and the detected-technologies list give visual context, and the findings list enumerates exactly what cost points. Work the findings from the top down, since the highest-severity items move the score the most.
Accepted trackers from the Always-Active Trackers allowlist appear here as notes rather than deductions, so a clean opt-out configuration is not penalized for behavior the client deliberately chose. Resolve the genuine findings, rescan, and watch the score climb toward the next tier.
Allowlisting an intentionally always-on tracker keeps it from counting as a violation, which protects the score for clients running a US opt-out model. Pair this with a Breach Threshold in the Notifications panel so you get an email whenever the score drops below the level you care about.
Troubleshooting
The tile shows Not Scanned
A Not Scanned status means no completed scan has produced a score for this project yet. Run a scan from the project, wait for it to finish, and the Privacy Score and tier will populate from the new run.
The score seems low despite a deliberate opt-out setup
If the client legitimately runs trackers always-on under a US opt-out model, those pixels are being counted as violations until you allowlist them. Open the Always-Active Trackers panel, select the trackers the client intends to run, save, and rescan so they convert from deductions into accepted notes.