Google is deprecating their "Universal Analytics" platform and will stop accepting new data on July 1, 2023. They're encouraging everyone to move to Google Analytics 4. It's possible to submit data to both in parallel to help with the migration and reporting conversion.

https://blog.google/products/marketingplatform/analytics/new-way-unify-app-and-website-measurement-google-analytics/

They have a number of migration documents including:

https://support.google.com/analytics/answer/10089681

https://support.google.com/analytics/answer/10759417

https://support.google.com/analytics/answer/9744165

This will probably warrant a full spec when we're ready to tackle it, but at a high level will probably include:

1. Adding new options to our Analytics settings that pull in the new JS dependency and propagate the right context.
2. Updating servers that have custom analytics scripts.
3. Updating Content-Security-Policy headers to allow data pass-through.

Unsure of the best sponsoring budget so tagging a number of potentially interested parties.

Seems more like CI to me

I've been asked by one client about this already. I will add a new metric to give us info on where this is used to help prioritize. https://github.com/LabKey/platform/pull/3311

New metric will be part of 22.6 and beyond. It's analyticsTrackingStatus in the Core module. "disabled" is the default and indicates there's no analytics enabled. "enabled" and "enabledFullURL" are both old-style Google Analytics. "script" is a customized analytics script that could be GA and/or anything else.

Thanks Josh. We will review this once we are receiving metrics.
Bernie

I got customer pushback on my plan to make any real changes in 22.11 so I went ahead and got this working with GA4 and also changed the configuration to allow selecting multiple approaches at once. This will be useful to let servers double-report to old and new versions for a transition period.