This app enhances incoming events by including browser & OS details from the
Note: This app is generally only needed when using clients that don't already set these properties, or when sending events directly from the server.
This app extracts the following properties from the provided
|Name of the browser for the user||Chrome, Firefox|
|The version of the browser that was used||70, 79|
|The operating system of the user||Windows, Mac OS X|
|The type of client that made the request||bot, browser|
PostHog Cloud users can find the app here in their dashboard.
Before you can enable the app, you will need to configure it by clicking on the settings icon. Once the app has been configured, you can enable it by flipping the toggle and it will start transforming all new events.
- Visit the 'Apps' page in your instance of PostHog.
- Search for 'User Agent Populator'.
- Configure the app by clicking on the settings icon.
- Click the toggle to enable the app.
Once the app has been configured and enabled, it will begin to transform all new events which come into PostHog.
Before an app can be enabled in PostHog, it has to be configured.
|If the ingested event already have $browser $browser_version properties in combination with $useragent the $browser, $browser_version properties will be re-populated with the value of $useragent|
|Segment's analytics.js library automatically sends a useragent property that Posthog sees as segment_userAgent. Enabling this causes this plugin to parse that property|
Using the User Agent Populator
This app works by parsing the
$useragent property on events as they are ingested.
As a result, if an event is ingested without the
$user-agent) property set, this app will do nothing.
This property can be set using any of our client or server libraries.
Note: Most of our client libraries will already automatically extract the
$osproperties, so there is no need to set the
$useragentproperty when using these libraries.
One common use-case for this app is populating client information when sending events from the server-side. Typically, a
UserAgent header will be set when a client sends a request to your server, which your server can then forward to PostHog with the
This gives you an idea of what types of clients are using your service and allows you to create insights that filter based on these properties.
What if my question isn't answered above?
We love answering questions. Ask us anything via our Questions page or using the Q&A widget at the bottom of this page.
You can also join the PostHog Community Slack group to collaborate with others and get advice on developing your own PostHog apps.
Who created this app?
This app was created by the community. We'd like to thank Weyert for creating the User Agent Populator, as well as for all the other support and feedback. Thank you, Weyert!
Who maintains this app?
This app is maintained by the community. If you have issues with the app not functioning as intended, please raise an issue on the repo.
What if I have feedback on this app?
We love feature requests and feedback! Please create an issue to tell us what you think.