Google Analytics isAnonymizedIpActive always true

[apomili]

Preconditions (*)

1 - Magento ver. 2.2.7 (and below, I suppose)
2 - Google Analycs correctly activated and Anonymize Ip turned to off.

Steps to reproduce (*)

1 - Install and activate GA Debbugger chrome extension
2 - Open the chrome console and browse the shop

Expected result (*)

GA set with no ip anon

Actual result (*)

Running command: ga("set", "anonymizeIp", true)

---

The bug seems to be in the file google-analytics.js on the google-analytic module.
On the line 51 the condition is always verified cause config.pageTrackingData.isAnonymizedIpActive is a string

[magento-engcom-team]

Hi @apomili. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@apomili do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

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

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

[ghost]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @engcom-backlog-nazar, here is your Magento instance.
Admin access: https://i-21292-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ghost]

Hi @apomili thank you for you report, i'm not able to reproduce following steps you described, on clean magento 2.3-develop instance

[apomili]

The variable in ga.phtml is passed correcty, but when is checked in the file google-analitycs .js

if (config.pageTrackingData.isAnonymizedIpActive) { ga('set', 'anonymizeIp', true); }

the condition is always true

[magento-engcom-team]

✅ Confirmed by @Nazar65
Thank you for verifying the issue! 👍 Your confirmation will help us to acknowledge and process this report.

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98312, MAGETWO-98313 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @apomili. Thank you for your report.
The issue has been fixed in #21303 by @Nazar65 in 2.3-develop branch
Related commit(s):

• edb9c6ebbb92fd97d953a4160d6b48e6654af448
• 1e86f88082360477a56d3beff6fd3d5c877ddaab
• 67ea734015ceab3aa05f740a55e5689450e3f1cd

The fix will be available with the upcoming 2.3.2 release.