- Issue created by @amangrover90
- @amangrover90 opened merge request.
- Status changed to Needs review
over 2 years ago 3:01pm 27 March 2023 - Status changed to Needs work
over 2 years ago 4:15pm 27 March 2023 - 🇺🇸United States mglaman WI, USA
Left some reviews. Looks great. It's basically just tidying up that remains.
- Status changed to Needs review
over 2 years ago 1:16pm 28 March 2023 -
mglaman →
committed 125b7169 on 2.0.x authored by
amangrover90 →
Issue #3350675 by amangrover90: Google Analytics 4.x migration
-
mglaman →
committed 125b7169 on 2.0.x authored by
amangrover90 →
- Status changed to Fixed
over 2 years ago 2:11pm 29 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
12 days ago 3:54pm 21 July 2025 - 🇦🇹Austria mvonfrie
Sorry, but I have to complain about how this issue has been dealt with.
Neither the issue title ("Google Analytics 4.x migration", which is the only available information about this issue in the 2.0.0 release notes) nor the description ("Upgrade path for users who want to upgrade to Google Tag 2.x from Google Analytics 4.x.") gives a hint about the fact that a part of its implementation (#fdbf66d5) disables all functionality of the Google Analytics module.
This is a breaking change!We just figured out that our customer lost around 1.5 years of Analytics data since we've updated both their sites from 8.x-1.8 to 2.0.0 and they did not want to configure it via GTM but keep it separate. We don't have access to their Analytics and GTM but just got the IDs from them, and they didn't notice it until a new member in their marketing department wanted to analyze the data.
For some developers here it might be just a simple (and maybe obvious) code change, but for users of the module it can mean a lot of money (or the loss of it)!
