ACSD-48634: JS errors when Google Analytics Content Experiments enabled

The ACSD-48634 patch fixes JS errors on a staging update page when Google Analytics Content Experiments is enabled. This patch is available when the Quality Patches Tool (QPT) 1.1.27 is installed. The patch ID is ACSD-48634. Please note that the issue was fixed in Adobe Commerce 2.4.7.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.5

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.3.7 - 2.4.6

The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the QPT landing page. Use the patch ID as a search keyword to locate the patch.


JS errors occur on a staging update page when Google Analytics Content Experiments is enabled.

Steps to reproduce:

  1. In Admin > Stores > All Stores, create an additional website, store, and Store View. Make sure the Store View is Enabled.
  2. Configure Configure Google Analytics by going to Stores > Settings > Configuration > Sales > Google API:
    • For Main and additional websites scope:
      • Enabled: Yes
      • Account type: Google Tag Manager
      • Anonymize IP: Yes
      • Enable Content Experiments: Yes
      • Container Id: (GTM container ID)
      • Uncheck Use Default for other fields, but do not change them.
    • For Default Config scope:
      • Enabled: Yes
      • Account type: Universal Analytics
      • Account Number: (Universal Analytics account number)
      • Anonymize IP: Yes
      • Enable Content Experiments: Yes
  3. Disable Configure Google Analytics on Default Config scope by changing Enable from Yes to No. Make sure not to change anything else!
  4. Go to Catalog > Categories.
  5. Create and Edit any category and add a scheduled update for it:
    • Any name, start date in the future, end date in the future, and any change in category (For Example: disable category).
  6. Save the update and check the browser developer console for errors.

Expected results:

No JS errors and the changes to the staging update are saved successfully.

Actual results:

JS errors are visible in the console, the form is malformed, and the spinner never gets disabled after the save.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

For info about other patches available in QPT, refer to Patches available in QPT in the Quality Patches Tool guide.

On this page