Migrate to allowlist and blocklist

Created on 21 February 2023, almost 2 years ago

Problem/Motivation

Google Tag Manager is migrating from 'whitelist' and 'blacklist' to 'allowlist' and 'blocklist' as seen here.

Proposed resolution

Change the code to reflect the new preferred terms instead of the old ones.

Remaining tasks

Discuss solution, create patch & commit

✨ Feature request
Status

Active

Version

1.6

Component

Code

Created by

πŸ‡¨πŸ‡·Costa Rica melisa.cordero

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @melisa.cordero
  • πŸ‡ΊπŸ‡ΈUnited States japerry KVUO

    This will likely not happen in the 8.x-1.x version, but has been changed as part of the upcoming 2.0 version. According to Google, they won't be removing the old parameters so there isn't a technical need to move away from it in a minor release.

  • I'm getting so frustrated with this damn Module.

    After suffering a 5 month Google Analytics outage due to the Consent Mode bug, I discovered that most tags in Google Tag Manager have not been firing since we installed 2.0.5 to resolve the earlier outage.

    It looks like all variables are wiped out when a GTAG command is sent to the datalayer. The command involves the allowlist and blocklist.

    Because the variables are all undefined (and never recover), Tags can't operate.

    I spent about 8 months in 2024 trying to resolve Google Analytics problems as a result of the Google Tag Module. This is ridiculous, and Acquia and Google are absent, clueless supporters.

Production build 0.71.5 2024