What does real-device web assurance cover, and when do you need it?

Availability, consent and device compatibility are usually handled by different teams with different tools: operations watches availability, legal or marketing owns the cookie banner, and QA tests on whatever devices are at hand. Each tool answers from its own vantage point, and most of those vantage points are not a customer's phone.

Running the three checks from the same kind of real device gives one consistent picture. When a page loads slowly on a real phone, sets advertising cookies before consent and shows a challenge page to mobile carrier traffic, those are three findings about the same visit, not three reports that are hard to reconcile.

Availability: URL load, DNS, TLS, HTTP result, redirect chain, detection of challenges or 403 pages, time to load and a screenshot. Consent: whether the banner appears, which options it shows, cookies before and after consent, and screenshots of each state.

Device compatibility: the device profile (model, OS, memory, cores, free storage and observed tier), navigation timing such as first contentful paint, memory use, janky frames and visible failures such as crashes or "app not responding" events, each with a screenshot.

Not every site needs all three. A content site with little mobile revenue may only need availability. A site already confident about its consent setup may only need occasional evidence runs. A bundle makes sense when all three questions matter and the same people need to read the answers together.

A practical sign that a real-device view is missing is a support queue that reports problems the dashboards do not show: customers who cannot reach checkout from their phones, cookie questions from the privacy team, or crash reports concentrated on older devices. Those are exactly the gaps between a datacenter's view and a customer's.

Web Assurance is coming soon. It becomes available only when each of its three components passes its own gate, and Low-end Device Check has not passed yet. Access Monitor and Consent & Cookie Check can already be used separately.

The bundle measures exactly what its components measure, on physical Android phones with real SIMs, with every run signed with Ed25519 and a single dashboard and invoice. An AI visual change feature is planned but not validated, and it is not part of the core service.

The limits of each component carry over: Access Monitor checks technical availability, not business content; Consent & Cookie Check is supporting evidence for visitors outside the EU, not a legal opinion; Low-end Device Check reports the device tier it actually ran on.