Problem/Motivation

Upgrade path for users who want to upgrade to Google Tag 2.x from Google Analytics 4.x.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork google_tag-3350675

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

amangrover90 created an issue. See original summary.

amangrover90 opened merge request !30

amangrover90’s picture

amangrover90 commented
Status: Active » Needs review
mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented
Status: Needs review » Needs work

Left some reviews. Looks great. It's basically just tidying up that remains.

amangrover90’s picture

amangrover90 commented
Status: Needs work » Needs review
mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented

Left more feedback

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented
Status: Needs review » Fixed

Fixed! Thanks.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

mvonfrie’s picture

mvonfrie commented

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)!