That plugin is no longer included by default in the sp.js build, and from my observations, rarely used when people use the browser-tracker directly, likely due to its size.
I think this value is valuable to have as a datapoint, because it enables using the derived_tstamp to actually measure the "time of day" a user is on a site without having to guess based on the region determined via GeoIP.
This adds a default to the tracker that should provide a good estimate for this value even without the use of the Timezone plugin, based on the configured timezone information available via the Internationalization API.
If the Timezone plugin is in use, it will override the value with whatever it determines.
This adds a more lightweight way for the browser-tracker to get a value for the
os_timezone
/tz
field that doesn't rely on the usual Timezone plugin.The Timezone plugin is very data-heavy, and when minified is currently the 4th largest plugin we distribute, but populates only this single field:
That plugin is no longer included by default in the
sp.js
build, and from my observations, rarely used when people use thebrowser-tracker
directly, likely due to its size.I think this value is valuable to have as a datapoint, because it enables using the
derived_tstamp
to actually measure the "time of day" a user is on a site without having to guess based on the region determined via GeoIP. This adds a default to the tracker that should provide a good estimate for this value even without the use of the Timezone plugin, based on the configured timezone information available via the Internationalization API. If the Timezone plugin is in use, it will override the value with whatever it determines.