Introduction🔗
The OpenRTB 2.6 specification defines a Structured User Agent (device.sua) format for representing User-Agent Client Hints. This is commonly used in programmatic advertising and real-time bidding scenarios.
Pass SUA to Device Detection🔗
If you receive UA-CH data in the SUA format, you can pass it directly to the device detection engine with the query. or cookie. prefix:
flowData.AddEvidence("query.51D_StructuredUserAgent", suaJsonString);
SUA format🔗
The SUA format looks like this:
{
"browsers": [
{"brand": "Chromium", "version": ["130", "0", "6723", "92"]},
{"brand": "Google Chrome", "version": ["130", "0", "6723", "92"]}
],
"platform": {"brand": "macOS", "version": ["15", "1", "0"]},
"mobile": 0,
"model": "",
"architecture": "arm"
}
Technical details🔗
The SUA format is converted internally to the equivalent Sec-CH-UA-* HTTP headers before processing:
Sec-CH-UASec-CH-UA-MobileSec-CH-UA-PlatformSec-CH-UA-ModelSec-CH-UA-Full-Version-ListSec-CH-UA-Platform-VersionSec-CH-UA-ArchSec-CH-UA-Bitness
The device detection engine converts SUA evidence in its C layer. You do not need additional pipeline elements or preprocessing steps.
Related pages🔗
For more details on OpenRTB integration, see the OpenRTB Mappings page.
For alternative UA-CH approaches, see:
- JavaScript API - using
getHighEntropyValues() - HTTP Headers - using
Sec-CH-UA-*headers