Google Universal Analytics will be EOL July 2023

[rhoerr]

Summary (*)

Per https://support.google.com/analytics/answer/11583528 (at time of writing):

Universal Analytics will be going away

Google Analytics 4 is our next-generation measurement solution, and it's replacing Universal Analytics. On July 1, 2023, standard Universal Analytics properties will stop processing new hits. If you still rely on Universal Analytics, we recommend that you prepare to use Google Analytics 4 going forward.

Understand what's going to happen

Until July 1, 2023, you can continue to use and collect new data in your Universal Analytics properties.
After July 1, 2023, you'll be able to access your previously processed data in your Universal Analytics property for at least six months. We know your data is important to you, and we strongly encourage you to export your historical reports during this time.

Magento_GoogleAnalytics currently implements analytics.js and its associated ga(...) function calls. Based on the info above, starting 2023-07-01, that will become completely nonfunctional (no longer collecting data). Continuing to use Google Analytics services will require implementing Google Analytics 4, which uses gtag.js and gtag(...) calls with event-based tracking.

This affects all Magento and Adobe Commerce installations 2.0 to 2.4.

Examples (*)

Magento_GoogleAnalytics currently uses analytics.js for Universal Analytics:

            (function (i, s, o, g, r, a, m) {
                i.GoogleAnalyticsObject = r;
                i[r] = i[r] || function () {
                        (i[r].q = i[r].q || []).push(arguments)
                    }, i[r].l = 1 * new Date();
                a = s.createElement(o),
                    m = s.getElementsByTagName(o)[0];
                a.async = 1;
                a.src = g;
                m.parentNode.insertBefore(a, m)
            })(window, document, 'script', '//www.google-analytics.com/analytics.js', 'ga');

            // Process page info
            ga('create', config.pageTrackingData.accountId, 'auto');

Per above, in July 2023, this will stop collecting data and no longer function as intended.

Proposed solution

Implement Google Analytics 4 far in advance of 2023-07-01 to allow merchants to transition to the new data collection platform.

Implementing GA4 will require total overhaul of the current implementation: https://support.google.com/analytics/answer/10119380?hl=en&ref_topic=11192706

See also

Deprecation/EOL notice: https://support.google.com/analytics/answer/11583528
Migration guide: https://support.google.com/analytics/answer/10759417?hl=en&ref_topic=10737980
Previously reported in #12941

---

• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.

[m2-assistant]

Hi @rhoerr. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @rhoerr,

Thanks for posting the issue!

We have tried to reproduce the issue in Magento 2.4-develop branch and found that currently, Magento uses Google Universal Analytics, please refer to the below:

magento2/app/code/Magento/GoogleAnalytics/view/frontend/web/js/google-analytics.js

Line 36 in bbaa528

(function (i, s, o, g, r, a, m) {

Hence confirming the issue.

Thanks

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.magento.com/browse/AC-2685 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Bashev]

This is already in development on this issue #32623