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.
Get in touch
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
Buyers can now put Experian’s audience and contextual intelligence to work in Google Ad Manager Curation in two ways: through off-the-shelf solutions available directly in Google Ad Manager, or through Custom Curation packages that Experian builds using Google Ad Manager’s inventory supply. Together, these options bring Experian’s consumer data foundation closer to the Google supply agencies already buy, with the flexibility to choose between a ready-to-use solution and an Experian package tailored to specific campaign goals. Why targeting at the source matters Many audience strategies still apply targeting on the buy side, which means signals pass through multiple systems before an impression is evaluated. Each step can shrink the pool of requests where the audience is still recognizable, so a carefully built strategy can reach the auction at a fraction of the scale it started with. Google Ad Manager Curation moves segment evaluation closer to the ad request. When a request matches the selected Experian segment, Ad Manager sends the bid request with the associated Deal ID to the buyer’s DSP. This more direct path can support stronger match and deal-transaction rates, more accurate forecasting, and better access to the audience defined in the strategy. As AI shapes more media decisions, the quality and provenance of the data feeding those systems matter more. Evaluating audience or contextual criteria closer to the source helps preserve the connection between the strategy and the impression being considered. Two ways to get started The right entry point depends on how much customization the campaign requires. Buyers can access Experian solutions off-the-shelf directly in Google Ad Manager or work with Experian to build a Custom Curation package using Google Ad Manager inventory supply. Start off-the-shelf For buyers who want direct, self-service access to Experian audience and contextual solutions. Experian solutions are available off-the-shelf in Google Ad Manager, giving buyers a straightforward way to select the data or contextual strategy that fits their campaign and create packages through Google Ad Manager’s Curation capabilities. Experian Audiences Experian Audiences draw on a deterministic offline identity foundation that represents more than 250 million U.S. consumers and 126 million U.S. households. Buyers can choose from Experian’s Audiences spanning demographics, lifestyle, financial signals, media habits, and household characteristics. That depth adds real-world consumer context beyond digital behavior alone. Contextual Experian contextual solutions give buyers a way to reach relevant environments without relying on identity. Buyers can select contextual audiences aligned to specific interests, categories, and content to inform where media appears. Experian also offers Predictive Indexed, which uses Experian audiences to predict the contextual categories and pages to target based on the likelihood that consumers visiting those environments fall within the selected audience. This gives buyers an audience-informed way to approach contextual activation without requiring identity at the point of activation. Build a Custom Curation package For buyers who need a strategy tailored to specific audience, contextual, and inventory requirements. Experian can build Custom Curation packages using Google Ad Manager’s inventory supply based on the targeting criteria that matter for a campaign. Where off-the-shelf solutions draw on Experian data, custom packages can also incorporate partner audiences and a brand’s own first-party audiences. Packages can combine Experian audiences, partner audiences, a brand’s own first-party audiences, contextual signals, and inventory or site criteria. Experian applies those criteria against Google Ad Manager inventory supply and brings the data, targeting, and inventory together into a single curated deal. This gives buyers a way to combine audience and supply decisions rather than managing each component separately. The approach can be tailored to the campaign. A buyer might start with a defined audience and add contextual or inventory criteria, bring a brand’s established first-party audience into the strategy, or build around specific supply and audience-quality requirements. Choose the path that fits the campaign Both paths do the same underlying thing: they move the audience or contextual decision closer to the ad request, before signal loss builds across the path. Whether a campaign calls for something ready to use or a package built to spec, the result is a more direct line from strategy to impression. Ready to get started? Explore Experian solutions available off-the-shelf in Google Ad Manager or contact your Experian representative to request a Custom Curation package. Latest posts
See how Experian helped FanThreeSixty clean, match, and enrich 7.6 million fan records through data enrichment and identity resolution.
What commerce media networks should look for in commerce media data partners, and how to test a provider’s structural neutrality.