User-Agent Strings

The user-agent string allows your app to identify the browser version, device make/model/supported software, and the version of Firebolt®. This uniform user-agent string will simplify app development and harmonize across all devices, including Sky, Xfinity, and Xumo. Additionally, this user-agent string meets IAB’s OTT Device recommendation to differentiate connected TVs and streaming devices.

The user-agent string follows the following pattern:

<browser> ComcastAppPlatform <device model> Firebolt/<firebolt version> 

• Browser = The browser used by the device.

• ComcastAppPlatform = The connected OTT device (e.g.: STB, TV, etc).

• Device Model= The make and model of the device.

• Firebolt/<version> = The current version of Firebolt® running on the device.

Example Xfinity Arris Xi6​

Mozilla/5.0 (Linux; x86_64 GNU/Linux) AppleWebKit/601.1 (KHTML, like Gecko) Version/8.0 Safari/601.1 WPE ComcastAppPlatform AX061AEI Firebolt/0.8.1​ 

Example Sky Titan v2​

Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.9.7 Chrome/56.0.2924.122 Safari/537.36 ComcastAppPlatform ES340UK Firebolt/0.6 

Targeting app versions

To effectively target an app version, the partner can follow these steps using the Firebolt® API:

1. Determine the version of the app to load.

2. Assess device capabilities (performance levels and make/model).

3. Based on device capabilities, the app should use the appropriate device APIs.

Note: Advertisers who want more detailed info, such as those found within SIS (operator, experience, and so on), must choose to adopt Firebolt or the AdvertisingSDK to receive this level of data via API.

Legacy custom user-agent strings

If your App has already been released using a different user-agent string format, please work with your partner manager to coordinate an appropriate switchover date.

What changes need to be made?

The current user-agent string typically contains less information, so in most cases, nothing will need to change, and the new user-agent string should not disrupt your App.

• If your analytics/telemetry segments are by UAS, you must adjust the “fingerprint” after the user-agent change.

• If your App relies on any user-agent parameters to target/profile, please coordinate with your partner manager to adopt Firebolt® APIs to continue access to those parameters.

• If your App requires a custom user-agent string for operational purposes, evaluate options with your partner manager.

Does my app need to use Firebolt® to move to the new user-agent string?

No. Although the new user-agent string identifies the supported Firebolt® version, this is a courtesy to Apps that have adopted Firebolt®. Apps may use this parameter to load the appropriate Firebolt® packages. Apps that don’t utilize Firebolt® can continue as is, ignoring the presence of the Firebolt value in the user-agent string.

Xumo & Sky devices

Other supported devices