INSIDE 3.3
VIS-004

Browser language and device context

Browser, language, time zone and page timing information help you understand a visitor's technical context.

developeroperatorsupervisor
DraftThis article hasn't been reviewed yet.
Where to find it
Floor › Summary

What it is

INSIDE collects technical context from the visitor's browser, including device type, browser language and time zone. Where the browser supplies it, page tracking also includes loading measurements. This helps you understand the visitor's environment when providing support.

Who uses it and why

  • Operators check the visitor's browser and language when explaining steps or choosing a chat language.
  • Supervisors use technical context when investigating recurring service issues.
  • Developers check whether the website integration supplies the expected context.

Where to find it

Open a visitor's Summary. It includes browser and operating-system information where detected, Browser Language, Chat Language and Time Zone. Ask Powerfront to inspect page timing information when investigating a loading problem.

How it works

The browser tracker supplies device and browser information, language, time zone offset and screen dimensions. INSIDE distinguishes desktop, mobile, tablet and console browsing, and recognises supported mobile-app identifiers.

Browser language and chat language are separate. You can change Chat Language without changing the language reported by the browser. Website mappings and chat-language configuration can also affect the chosen language.

Where browser timing information is available, the tracker measures request wait, response download, loading until the page becomes interactive, loading until completion and overall page loading. Values are in milliseconds. These describe the host page's loading, rather than the speed of an operator's reply.

Audio and video capability detection depends on enabled calling features and browser support.

Configure it

Technical context is collected by the website integration; there is no general device-context editor. Your developer should check the integration when expected values are missing. Use Chat Language in the visitor's Summary when the chat language needs changing.

Limits and good to know

  • Browser-reported information can be missing or incomplete.
  • An absent time zone offset is treated as zero. A GMT display does not verify the visitor's residence or location.
  • Page timing requires browser timing support. An invalid supplied timing value prevents the supplied timing set from being accepted.
  • Screen dimensions being sent does not mean every operator screen displays them.
  • Detected device and browser details describe the reported environment; they are not a verified hardware inventory.

Depends on and works with

RequiresConfigured byEnhances
View all connections as a list

This feature uses

Used by

FAQ and troubleshooting

Why are Browser Language and Chat Language different?

The first comes from the browser. The second can reflect a language selection, mapping or operator override.

Why are page loading measurements missing?

The browser or integration may not supply usable timing information. Ask Powerfront to check the captured context.

Does a GMT time zone mean the visitor is in the UK?

No. A missing offset can display as GMT, and a time zone is separate from geographic location.

Does video support mean the visitor has agreed to a call?

No. Technical capability and the visitor's decision to join a call are separate.

INSIDE 3.3 · Source commit 992abb980bContent is a pre-release draft© 2026 Powerfront