Learn business growth with Google Analytics 4 › Forums › Google Analytics 4 › Troubleshooting the issue of (other) language in Google Analytics 4 during migration from Universal Analytics › Reply To: Troubleshooting the issue of (other) language in Google Analytics 4 during migration from Universal Analytics
-
The issue here seems to be due to the transition from Universal Analytics to Google Analytics 4. In Google Analytics 4, the method for tracking user language has changed and it doesn’t appear to support the “set” command anymore. Instead, Google Analytics 4 now auto-tracks user language using the browser’s language setting, and the ‘language’ parameter is not a recognized parameter in a ‘page_view’ event. One workaround for this might be to create a new event specifically for tracking your custom ‘language’ parameter, and then create a custom definition for ‘language’ in the Google Analytics 4 interface. However, be aware that Google might still categorize some data as “(other)” if it doesn’t meet their data thresholds or quality standards. A more technically complicated but more reliable way would be pulling the client’s language information directly from the browser’s Navigator API and sending it as a custom parameter in your GA4 events. Documentation on how to track customized data with Google Analytics 4 could also provide more guidance.