Skip to main content
DeviceAtlas DeviceAtlas
  • Login
  • Get started
  • Products
    • Web
      DeviceAtlas for Web

      Build enterprise grade device awareness

      into your products and services

    • Apps
      DeviceAtlas for Apps

      Device intelligence, targeting and reporting

      in the native apps environment

    • Operators
      Device Map

      Fine grained device intelligence

      indexed by TAC/IMEI

    • DeviceAssure
      DeviceAssure

      Verify the authenticity of devices

      accessing your content and services

    • DeviceAtlas Discover
      DeviceAtlas Discover

      Rich insights about your web traffic that

      analytics platforms don’t tell you about

    DEVICE INTELLIGENCE

    Learn more with our
    intro video

    Deliver an amazing customer
    experience across devices.

    TECHNOLOGY OVERVIEW

    Get an overview of our technology.

  • Use Cases
    • Ad-Tech
      AdTech

      Enable granular device targeting of your campaigns.

      Maximize revenue from impressions and reduce discrepancies

    • Optimization
      Web Optimization

      Ensure content is delivered in a form that’s

      optimized for the end user’s device

    • Analytics
      Analytics

      Understand customer engagement at

      device level

    • Internet of Things
      Internet of Things

      Measure IoT activity on your network

    • OTT Streaming
      Online Streaming Services

      Identity OTT traffic from STBs, Smart

      TVs, and Games Consoles

    • eCommerce
      eCommerce

      Identify factors affecting cart abandonment rates, and ensure optimal user experiences for mobile devices.

    • Gaming
      Gaming

      Enhance knowledge of gaming devices for better analytics and reporting, real-time QoS/QoE monitoring, and more relevant targeting opportunities.

    • Reverse Logistics
      Reverse Logistics

      -

    • Device Insurance
      Device Insurance

      -

    CASE STUDIES

    Learn how market
    leaders are using us
    to outperform their
    competition

    Adoppler and our partners have experienced significant improvements since implementing DeviceAtlas.

    Anton Tkachuk

    Product Manager, Adoppler

    View all case studies

  • Pricing
  • Developers
    • Technology Overview

      Get an overview of our technology

    • Getting Started

      Step by step guide to get up and running fast

    • APIs

      Downloads and information on all APIs

    • About the data

      Device data and available properties

    • Docs & Support

      FAQ's documentation and support

    • Knowledge Base

      Explore our expansive library of free

      whitepapers, eBooks and how-to guide

  • Data & Insights
    • Blog

      Stay informed with our articles on device

      research, data and insights

    • Case Studies

      See why market leaders choose DeviceAtlas

    • Device Browser

      Device information and properties

    • Data Explorer

      Explore and analyse DeviceAtlas data

    • Properties

      Check out our available device properties

    • HTTP Headers Parser

      Check DeviceAtlas results for HTTP Headers

  • Login
  • Get started
Log inSign up
Forgot Password?

Sign up below to view device data and get your trial account.

Passwords match:

Cancel
  • Products
    • DeviceAtlas for Web
    • DeviceAtlas for Apps
    • Device Map
    • DeviceAssure
    • DeviceAtlas Discover
    • Technology Overview
  • Use Cases
    • AdTech
    • Web Optimization
    • Analytics
    • Internet of Things
    • Online Streaming Services
    • eCommerce
    • Gaming
    • Reverse Logistics
    • Device Insurance
    • Case Studies
  • Pricing
  • Developers
    • Technology Overview
    • Getting Started
    • APIs
    • About the Data
    • Docs & Support
    • Knowledge Base
  • Data & Insights
    • Blog
    • Case Studies
    • Device Browser
    • Data Explorer
    • Properties
    • HTTP Headers Parser
  • Login
  • Get started
  • Search

Getting Started

  • Enterprise
    • DeviceAtlas for Web
    • DeviceAtlas for Apps
  • Cloud
  • DeviceAssure
    • DeviceAssure for Web
    • DeviceAssure for Apps
  • Discover

APIs

  • Enterprise APIs
    • Download API
    • Documentation
    • API examples
    • Performance
  • Cloud Service
    • Download API
    • Documentation
    • Cloud Service End-Points
    • Google Sheets Integration
  • DeviceAssure APIs
    • Download API
    • Documentation
  • Client-side Component
    • iOS H/W Identification
    • Usage
    • Download
  • REST API
  • User-Agent Client Hints
    • Developer considerations
    • Web server configuration
    • OpenRTB and UA-CH
    • Capturing in JavaScript
    • Header precedence logic

Data

  • Data Downloads
    • Carrier Data
    • Device Data (JSON)
    • Device Map (TAC)
  • Data File Configuration
  • Contributing
  • About Our Data
  • Dynamic Data
  • Becoming a Data Partner

Properties

  • Available Properties
  • Client-side Properties

FAQ

  • Support
  • General
  • Licensing

More

  • Side-loaded Browsers
  • Whitepapers
  • Case Studies

User-Agent Client Hints

What are Client Hints?

User-Agent Client Hints (UA-CH) is a Google proposal that changes how certain browsers identify themselves to web servers. In summary, the proposal removes granular information such as device model, operating system version and granular browser version details from the traditional User-Agent header by replacing these tokens in the User-Agent header with unchanging placeholders.

The following example shows the change to a typical Android phone (Huawei P30 Pro) User-Agent header, before and after the UA-CH change:

Mozilla/5.0 (Linux; Android 11; VOG-L09) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.4472.120 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 10; K)       AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0      Mobile Safari/537.36

In browsers supporting UA-CH the granular information thus removed can obtained in two ways:

  1. Via JavaScript APIs in the browser
  2. By requesting additional UA-CH headers to be sent by the browser with each subsequent request

The proposal is managed in the Web Incubator Community Group (WICG). The full specification can be read on the WICG's GitHub page along with a list of issues.

Since around May 2023 User-Agent Client Hints are now fully rolled out in current versions of Chrome and Edge. Web servers can thus expect a large proportion of traffic to present using these headers and a reduced User-Agent string. For Android devices in particular about 2/3 of web traffic for most websites is now sending reduced User-Agent headers and corresponding UA-CH headers.

Contents

The remainder of this page is divided into the following sections:

  • What are Client Hints?
  • DeviceAtlas support for User-Agent Client Hints
  • Developer considerations
    • Header precedence in DeviceAtlas
  • Capturing and processing UA-CHs
    • Configuring your web server to support UA-CH
    • Capturing of UA-CHs from JavaScript in HTTP header format
    • OpenRTB and UA-CH
    • Obtaining UA-CH in the first request
  • Testing tools

DeviceAtlas support for User-Agent Client Hints

DeviceAtlas fully supports User-Agent Client hints since version 3.0 of our SDK, available in all supported languages. The API is method-compatible with previous versions but the inherent nature of UA-CH means that developers should pass all UA-CH headers to the DeviceAtlas API in addition to the User-Agent header in order to maintain product functionality. 

Version 3 of the DeviceAtlas API consumes a differently-formatted data file than previous versions of the API. Customers can set this new format to be the default from their Account / Data File Options page. Alternatively, the file format can be specified with parameters to our download link. You can build data download URLs by testing options on our JSON Data File Download page.

Developer considerations

UA-CHs introduce many additional considerations for developers such as working around the first visit issue and delegating hints permissions for third-party origins and iframes. You can read more about these considerations in our User-Agent Client Hints Developer Considerations Guide. 

There are several different scenarios where the precedence of UA-CH and the User-Agent header must be considered. Our DeviceAtlas and UA-CH header precedence page describes the logic used by DeviceAtlas in different contexts. 

Capture and processing of User-Agent Client Hints

User-Agent Client Hints and JavaScript

UA-CHs are normally obtained from HTTP headers or via a JavaScript API in the browser. However, for some use cases it may be desirable to capture UA-CHs in JavaScript from the browser but in a header-like format that can then be sent to a server as part of an existing payload for analysis by DeviceAtlas. This code may be useful for customers with integrations with publishers, to share with their publisher partners to facilitate capture of client hints, or for publishers for their own use. You can read more about this in our Capturing User-Agent Client-Hint data from the browser with JavaScript guide. 

Configuring your web server to support User-Agent Client hints

Our Configuring NGINX and Apache to support User-Agent Client-Hints guide explains how to configure NGINX and Apache to request UA-CHs from visitors to your website.

OpenRTB and User-Agent Client Hints

The OpenRTB protocol has been updated to support UA-CH since version 2.6 of the specification was released in 2022. With the newest update, the OpenRTB specification now explicitly defines how to populate the ua attribute and the sua attribute in the case where a browser supports User-Agent Client Hints. You can read more about this in our blog post at the time.

SSPs and DSPs can learn how to convert back and forth between OpenRTB SUA objects and conventional HTTP headers with sample code from our User-Agent Client Hints and OpenRTB guide. These examples also cover the use case of parsing JavaScript-source userAgentData to the OpenRTB SUA format.

Obtaining UA-CH in the first request

Google have proposed a mechanism for obtaining UA-CH in the first request from a new browser by utilising the ALPS extension to TLS. Our Obtaining high-entropy User-Agent Client Hints in the first request page discusses the details. 

Testing tools

The DeviceAtlas Header Parser permits you to test any HTTP headers or to use and see all of the headers sent by your current browser, including User-Agent Client Hints.

User-Agent Tester

 

DeviceAtlas identifies and verifies connected devices in real-time for rich, actionable intelligence across every customer touchpoint

DeviceAtlas LinkedIn DeviceAtlas X DeviceAtlas YouTube

Our Products

DeviceAtlas for Web

The full picture on web traffic with detailed metadata on all visiting devices

DeviceAtlas for Apps

Device intelligence, targeting and reporting in the native apps environment

DeviceAssure

Real-time identification of fraudulent and misrepresented traffic

Device Map

TAC-based device insights for the mobile ecosystem, in partnership with the GSMA

Industries

AdTech Optimization Analytics Internet of Things OTT / Streaming eCommerce Gaming Reverse Logistics Device Insurance

Quick links

Pricing About us Events Blog Device Intelligence Device Detection Technology Partners Case Studies Data & Insights Developers Contact us

Copyright © DeviceAtlas Limited 2025. All Rights Reserved. Terms & Conditions | Privacy Policy

This is a website of DeviceAtlas Limited, a private company limited by shares, incorporated and registered in the Republic of Ireland with registered number 398040 and registered office at 6th Floor, 2 Grand Canal Square, Dublin 2, Ireland

Industry Affiliations