Open kreynen opened 2 years ago
If we are going to define a default 404 page that includes Search, we'll need to start looking at https://github.com/cu-uis/cu-starterkit-project/issues/48
https://support.google.com/analytics/answer/9744165?hl=en documents how to add GA4 while still running UA.
While it is unclear whether the false white space VRT failures on the CU Online are caused by Config Split differences, we should at least attempt to configure a site where the live and dev configuration match.
I configured a new GTM instance that adds the GA4 tag for https://github.com/cu-uis/cu-starterkit-project/issues/48 using the https://www.drupal.org/project/gtm module. That module adds the gtm code to the 404 and 403 responses by default. The way this is set up is GA4 is connected to GTM and CSE/Programmable Search has changed from how this was configured with GA Universal.
Is your feature request related to a problem? Please describe.
By default, sites running on cu.edu should be using a standard Google Analytics account that is broken up by Properties instead of creating and managing hundreds of site specific GA instances.
Describe the solution you'd like
With GA Universal EoL coming in 2023 all of our sites need to move or be upgraded to GA360 to extend the deadline until October 1, 2023. Rather than building new sites using the old GA approach, we should be including a default GTM configuration that uses GA4 and includes analytic tracking on 404s, 403s and potentially even 503 (if Pantheon Advanced Caching supports that).
Describe alternatives you've considered
The current GTM/GA configuration used on online.cu.edu.
Additional context
https://gitlab.cu.edu/uis-webdev/online-cu-starterkit/-/issues/477 https://gitlab.cu.edu/uis-webdev/online-cu-starterkit/-/issues/479 https://gitlab.cu.edu/uis-webdev/online-cu-starterkit/-/issues/480