User-Agent Derived Field Description

FunnelConnect uses across its Data Pipeline services Udger with local parser for User-Agent HTTP header to extract structured metadata about the client making the request. This information aids in analytics, compliance, and user experience optimisation.

Full Header

ua.hdr: The complete User-Agent string as received in the HTTP request.

Example:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36

Derived Fields

These fields are extracted from ua.hdr using Udger's parsing engine:

ua.bType: The general category of the client software.

ua.bFamily: The specific browser or client family.

Examples:

• CFNetwork

• Chrome

• Chrome Mobile

• Facebook App

• Firefox

• Google App

• Instagram App

• Klarna App

• Microsoft Edge

• Microsoft Edge mobile

• Mobile Samsung Browser

• Safari

• Safari mobile

• Silk
  

ua.bVer: The version number of the browser or client.

Examples:

• 136.0.0.0

• 18.5

• 368.0.756386193

• 514.0.0.47.102

ua.os: The operating system of the client device.

Examples:

• Android

• BSD

• Fire OS

• HarmonyOS

• Linux

• OS X

• OS/2

• PS5 OS

• Symbian OS

• Tizen

• Windows

• iOS

• macOS

ua.dName: The device class or type.

ua.latency: Lookup latency in msec with average latency below 1 msec.

Information for Business & Legal Teams

• Purpose: These fields help identify the type of client accessing your services, which is crucial for analytics, security, and compliance.

• Data Privacy: All derived fields are obtained from the User-Agent string, which is part of the HTTP request headers and does not contain personally identifiable information.

• Compliance: Understanding client types can aid in ensuring compliance with various digital accessibility and compatibility standards.

• Compliance: User Agent Data is only derived, collected and inlined by FunnelConnect if the configured consent checks are passed.