What is the ZDX Score?
The ZDX Score is the key metric in Zscaler Digital Experience (ZDX): it sums up the digital user experience as a single value between 0 and 100. The score combines signals from the device, the network and the application, showing at a glance whether users can work well: values from 66 up count as good (green), 34 to 65 as acceptable (yellow), and anything below that as poor (red). You can view it at several levels: per user, per application, per site, or for the whole organisation. That makes it both an early indicator and a starting point for troubleshooting. A falling score shows you where to look more closely, but it does not replace proper root-cause analysis with tools such as ZDX Deep Tracing.
ZDX Score in detail
Measurement happens through the Zscaler Client Connector on the endpoint: for the applications configured in ZDX, it runs regular measurements, for example of reachability and response time, and captures device metrics such as CPU, memory or Wi-Fi state at the same time, along with the network path towards the application. The score is built from these signals; Zscaler documents the exact composition and weighting in the ZDX documentation.
Important for interpretation: the score covers only the monitored applications. An application with no monitor configured for it does not appear in the score, no matter how badly it performs. The score also only becomes meaningful by comparison: against its own normal state, against other sites, against its trend over time. An absolute value without context says little; a sudden drop against the baseline, on the other hand, is a strong signal.
Why the ZDX Score matters in Zscaler operations
In day-to-day support, the ZDX Score is the fastest route to triage: when a user reports that 'everything is slow', a glance at the score shows whether the device, the network or the application is at fault, and whether only that user is affected or the whole site. That decides whether the ticket stays with the helpdesk, goes to the network team, or gets treated as a mass incident.
At the operational level, the score works as an early warning system and a reporting metric: if a site's experience deteriorates gradually, that shows up in the score trend before tickets start piling up. This depends on a well-maintained monitoring setup, with sensible application monitors, realistic thresholds and alerting. Without that, the score stays a number with no consequence; with it, the score becomes a shared reference point for the helpdesk, the network team and management.
Common sources of error
- Score without drill-down: reporting only the value, without looking into the device, the network path and the application, confuses the symptom with the cause.
- No baseline: an absolute score with no comparison to normal state, site and time of day leads to false alarms or false reassurance.
- Gaps in monitor coverage: critical applications with no monitor configured stay invisible; the score looks healthy even while users are struggling.
- Jumping to conclusions: a poor score does not automatically mean 'Zscaler is at fault'; the Wi-Fi, the ISP or the endpoint is often the real cause.
ZDX Score in practice: what CentaurNexus contributes
CentaurNexus turns the score into an answer: Connectivity Triage Map brings the ZDX chain and the policy status together and names the cause in plain language, whether that is the ISP, the Wi-Fi, the device or Zscaler. The helpdesk does not need to interpret the score itself; it receives the classification ready-made. The guide below shows how that cuts handling time: Is it Zscaler or the Wi-Fi?. User Support Center embeds the experience data into the 360-degree user diagnosis across ZIA, ZPA and ZDX, in a single view and without Zscaler admin rights. That is how the ZDX Score turns from an expert metric into an everyday tool for 1st Level.
Related terms
Frequently asked questions about the ZDX Score
The ZDX Score sums up the digital user experience in a single metric. It combines signals from the device, the network and the application for the monitored applications, showing whether users can work without disruption. It is a starting point for troubleshooting, not a substitute for detailed root-cause analysis.
The score is fed by measurements from the Zscaler Client Connector: application measurements such as reachability and response times, network path data, and device metrics. Zscaler documents the exact composition and weighting in the official ZDX documentation; look it up there rather than trying to infer it from the value itself.
Zscaler divides the value range into bands, which are described in the ZDX documentation. In practice, the comparison matters more than the absolute number: what counts is whether the score deviates from the normal state for the user, the site or the application, and whether several users are affected at the same time.
The score measures experience, not just availability. An application can be reachable while high latency, packet loss on the Wi-Fi, an overloaded endpoint or a degraded network path slows the work down. The score makes exactly these cases visible before users start talking about an outage.
Only the applications configured as monitors in ZDX. Unmonitored applications are not included, no matter how relevant they are. That is why rolling this out should start with a look at the application portfolio: business-critical services need sensible measurement points and thresholds in place.
- Zscaler Help Portal: ZDX documentation, help.zscaler.com/zdx
- Zscaler Help Portal: Understanding the ZDX Score - help.zscaler.com/zdx/understanding-zdx-score
Note: CentaurNexus is an independent product of SourcingBlox GmbH and not an offering of Zscaler, Inc. Product and brand names belong to their respective owners.