In 2022, Google began changing the availability of the information available in User-Agent strings across their Chromium browsers. The change is to use the set of HTTP request header fields called Client Hints. Through this process, a server can request, and if approved by the client, receive information that would have been previously freely available in the User-Agent string. This change is likely to have an impact on publishers across the open web that may use User-Agent information today.
To explain what this change means, how it will impact the AdTech industry, and what you can do to prepare, we spoke with Nate West, our Director of Product.
What is the difference between User-Agents and Client Hints?
A User-Agent (UA) is a string, or line of text, that identifies information about a web server’s browser and operating system. For example, it can indicate if a device is on Safari on a Mac or Chrome on Windows.
Here is an example UA string from a Mac laptop running Chrome:
To limit the passive fingerprinting of users, Google is reducing components of the UA strings in their Chromium browsers and introducing Client Hints. When there is a trusted relationship between first-party domain owners and third-party servers, Client Hints can be used to share the same data.
This transition began in early 2022 with bigger expected changes beginning in February 2023. You can see in the above example, Chrome/109.0.0.0, where browser version information is already no longer available from the UA string on this desktop Chrome browser.
How can you use User-Agent device attributes today?
UA string information can be used for a variety of reasons. It is a component in web servers that has been available for decades. In the AdTech space, it can be used in various ad targeting use cases. It can be used by publishers to better understand their audience. The shift to limit access and information shared is to prevent nefarious usage of the data.
What are the benefits of Client Hints?
By using Client Hints, a domain owner, or publisher, can manage access to data activity that occurs on their web properties. Having that control may be advantageous. The format of the information shared is also cleaner than parsing a string from User-Agents. Although, given that Client Hints are not the norm across all browsers, a long-term solution may be needed to manage UA strings and Client Hints.
An advantage of capturing and sharing Client Hint information is to be prepared and understand if there is any impact to your systems and processes. This will help with the currently planned transition by Google, but also should the full UA string become further restricted.
Who will be impacted by this change?
Publishers across the open web should lean in to understand this change and any potential impact to them. The programmatic ecosystem supporting real-time bidding (RTB) needs to continue pushing for adoption of OpenRTB 2.6, which supports the passing of client hint information in place of data from UA strings.
What is Google’s timeline for implementing Client Hints?
Do businesses have to implement Client Hints? What happens if they don’t?
Not capturing and sharing with trusted partners can impact capabilities in place today. Given Chromium browsers account for a sizable portion of web traffic, the impact will vary for each publisher and tech company in the ecosystem. I would assess how UA strings are in use today, where you may have security concerns or not, and look to get more information on how to maintain data sharing with trusted partners.
We can help you adopt Client Hints
Reach out to our Customer Success team at tapadcustomersuccess@experian.com to explore the best options to handle the User-Agent changes and implement Client Hints. As leaders in the AdTech space, we’re here to help you successfully make this transition. Together we can review the options available to put you and your team on the best path forward.
About our expert
Nate West, Director of Product
Nate West joined Experian in 2022 as the Director of Product for our identity graph. Nate focuses on making sure our partners maintain and grow identity resolution solutions today in an ever-changing future state. He has over a decade of experience working for media organizations and AdTech platforms.
Latest posts
Heading This is my content Heading This is my content Title sdf sdf sdf sdf sdf sdf sdf
Use case #1: Identifying customer spending potential to boost growth for a retail chain Objective A large retail chain wanted to understand the spending potential of each customer in their stores. Their goal was to uncover and maximize untapped spending potential. Solution The large retail chain licensed Marketing Attributes to identify the top demographic factors that drove spending in the retail store the previous year. The four key drivers were: Age, Income, Family structure (household composition), Location/region. Results By combining these attributes to create custom segments, we uncovered two valuable annual estimates: Potential spend: A conservative estimate of how much a customer could spend if they reached the top 20% of spenders within their specific demographic segment (based on data from the highest spenders). Unrealized spend: The difference between a customer’s annual potential spend and their current spend. An estimate of how much more they could be spending each year. The solution By syncing its cookies with the Digital Graph, the DSP gained access to related identifiers, including: MAIDs CTV Ids IP addresses Experian cookies This expanded identity universe gave the DSP a unified view of individuals and households, making it possible to connect impressions to conversions across devices and channels. With each weekly refresh, attribution models stayed accurate and up to date, turning fragmented signals into proof of performance. Results Within weeks, the DSP saw measurable improvements 84% of IDs synced 9% increase in match rates