Preparing for Chrome 110 and User-Agent Client Hints
In the next few weeks, one of the biggest changes to the underlying workings of the web in some time will begin to roll out. This little-noticed change could have far-reaching implications across the web ecosystem.
The Commercial Impact of Client Hints on Open-Source Parsers
We've all read Google's timeline for UA-CH and when changes are going to start coming into effect. But what will these changes mean for the open-source solutions and what impact is that going to have on the businesses relying on these solutions for commercial gain?
OpenRTB and User-Agent Client Hints
The IAB recently published an updated version of the OpenRTB specification. The updated document, a revision to version 2.6 of the specification, now addresses the landscape change brought about by Google’s decision to progressively reduce the content of the user-agent string in Chrome in favour of User Agent Client Hints (UA-CH).
DeviceAtlas HTTP Headers Parser
Learn how our updated HTTP Headers Parser tool can identify devices from both User Agent strings and Client Hints to provide a comprehensive solution to the changing User Agent Client Hints landscape.
[Webinar] User-Agent Strings and User Agent Client Hints: navigating the new landscape
Learn how DeviceAltas is evolving our service in line with Google's plans to deprecate and freeze UA strings in Chrome, with our support of both Client Hints and User Agent Strings using real-time analysis, which maximises coverage across browsers.
DeviceAtlas now supports Client Hints with our new UA-CH Model header service
DeviceAtlas uses all HTTP headers, now including Client Hints headers, to ensure maximum insights into device and browser capabilities in web traffic. This service is available to customers and prospects to try out on demand.
Client Hints and A High-Value Use Case
Learn more about Client Hints including the aim, background, limitations and get a key high-value use case that has calculable ROI, here.