Skip to main content

4.4

This page details the changes and new features introduced in Google Tag Manager for WHMCS version 4.4.X.

4.4.4​

  • Release date: 2026-10-24
  • Release type: Patch Release

v4.4.4 adds a setting for installations where something else already inserts the container on the page, such as Google tag gateway on Cloudflare. Without it, that setup loads the container twice and every hit is counted twice, which breaks conversion tracking.

The addon can leave the container to the CDN​

Google tag gateway for advertisers replaces the tag already present on the site. If the addon prints its own loader as well, the page requests the container twice, once from the gateway and once from the addon, and every event in the container is recorded twice.

The new Container Injection setting tells the addon that the container is already on the page:

  • This addon (default): the addon prints the loader and the noscript fallback. Nothing changes for existing installations.
  • Already on the page (CDN, tag gateway): the addon prints neither the loader nor the noscript, and keeps sending its data layer events, such as invoice view, purchase and customer data, to the container already on the page. In this mode the Custom Domain field is not used.

In the second mode the data layer is pushed into, never replaced, so the container stays attached to the data it receives.

Confirm that something injects the container

The server cannot detect whether the container is really being injected elsewhere: the replacement happens at the edge, after the page leaves WHMCS. If you select Already on the page and nothing injects the container, no container runs and nothing is tracked. The addon shows a warning on its configuration page while this mode is active.

4.4.3​

  • Release date: 2026-10-24
  • Release type: Patch Release

v4.4.3 makes the Custom Domain field accept the path a Google tag gateway uses to serve a container first-party.

The Custom Domain field accepts a first-party path​

Google tag gateway serves the container on a reserved path of the site, for example example.com/securemetric, and does not serve anything at /gtm.js. Entering only the host in the Custom Domain field made the page request https://example.com/gtm.js, which the gateway does not answer, so no container loaded and the tags stopped firing.

The field now accepts both shapes:

  • a host, such as gtm.example.com, which keeps Google's paths and requests /gtm.js
  • a host with a path, such as example.com/securemetric, which requests the container from that path and does not print the noscript fallback, since the gateway does not serve it

Query strings and fragments are still rejected, and the path is limited to 100 characters.

4.4.2​

  • Release date: 2026-10-22
  • Release type: Patch Release

v4.4.2 fixes the License Information panel and removes from the package libraries that WHMCS already loads. If you are running v4.4.1 you should update, especially if your WHMCS imports mail into the helpdesk from a cron job or if the addon page showed no License Status at all.

The License Information panel shows the state again​

On every installation the panel could show an empty License Status even when the license was valid. The module now displays the state, the reason, the time of the last check and the validity it has just computed, in the same request. If your license was ever reported as missing only because the panel was silent, nothing needs to be re-entered: this release makes the panel show what the module already knew.

The package no longer ships libraries WHMCS already provides​

v4.4.1 included a bundled copy of a library that WHMCS also loads. Its version took precedence at runtime and made one of WHMCS's own classes incompatible, which produced a fatal error on the cron that imports mail into the helpdesk. The package no longer includes those libraries, so there is nothing left to override on any WHMCS version.

4.4.1​

  • Release date: 2026-10-17
  • Release type: Patch Release

Google Tag Manager for WHMCS v4.4.1 replaces the v4.4.0 packages, which are withdrawn. With v4.4.0 the module could fail to load after installation, and on some installations that took the client area down. If you installed v4.4.0, update to v4.4.1.

The v4.4.0 packages are withdrawn​

With v4.4.0 the module could stop loading: the addon page could show an error and, depending on the installation, the client area could fail to render. Both packages, WHMCS 8.x and WHMCS 9.x, were affected. v4.4.0 must not be installed, and an installation already running it should be updated to v4.4.1.

Packages rebuilt and tested​

Both packages were rebuilt from the v4.4 source and tested on the PHP versions each one supports before publication. The package is self-contained: every library the module uses at runtime ships inside it, so tracking no longer depends on a component being present on the server.

The license check changes from v4.3.1 are included, so an installation coming from v4.3.0 gets them with this update.

Supported versions are unchanged​

  • WHMCS 8.x: PHP 7.4, 8.1, 8.2 and 8.3, with ionCube Loader 12 or later
  • WHMCS 9.x: PHP 8.2 and 8.3, with ionCube Loader 14 or later

Upgrade Notes​

Updating is a file swap: replace the module directory with the content of the package, and your Container ID and Google Analytics settings are kept. No database and no configuration changes.

If your client area is failing after a v4.4.0 update, restore the v4.3.0 package first, then install v4.4.1. See Upgrade.


Release Type: Patch (Stability)
Breaking Changes: None
License Requirements: Available in all license types

4.4.0​

Withdrawn

v4.4.0 was withdrawn in favour of v4.4.1. Do not install it. If it is already installed, update to v4.4.1: see the entry above.

  • Release date: 2026-10-06
  • Release type: Maintenance Release

Google Tag Manager for WHMCS v4.4.0 adds an encoded package for WHMCS 9. Nothing changes in how the module behaves inside WHMCS: this release carries the license check fix that shipped in 4.3.1, so installing 4.4.0 also gets you that fix.

Encoded Packages​

  • Encoded packages are produced for WHMCS 8.x (PHP 7.4, 8.1, 8.2 and 8.3, with ionCube Loader 12 or later) and for WHMCS 9.x (PHP 8.2 and 8.3, with ionCube Loader 14 or later)
  • The WHMCS 9 package is encoded with a minimum loader version of 14, matching what WHMCS 9 requires

Upgrade Notes​

No database changes and no configuration changes. Upgrading means replacing the module files, as described in Upgrade.


Release Type: Patch (Compatibility)
Breaking Changes: None
License Requirements: Available in all license types