BugWP logo BugWP
Back to Community
Home / Community / Plugin → Gtm4wp – a google tag manager (gtm) plugin for wordpress

Troubleshooting Common GTM4WP Plugin Errors: From Code Snippets to 503s

26 threads Sep 17, 2025 Plugin → Gtm4wp – a google tag manager (gtm) plugin for wordpress

Content

Users of the 'GTM4WP – A Google Tag Manager (GTM) plugin for WordPress' often report a range of errors that can disrupt their websites. Based on community discussions, here are some of the most frequent issues and their potential solutions.

1. Unwanted Code or Text Appearing on Pages

The Problem: Users frequently see unexpected text, JSON-like code snippets, or verification strings (e.g., google-site-verification:...) displayed at the bottom of their pages, typically in the footer.

Why it Happens: This is almost always related to the placement of the Google Tag Manager container code. The plugin offers options for where to place the <noscript> part of the GTM code. If this is misconfigured, or if a tag within your GTM container contains raw JavaScript code not wrapped in a <script> tag, it can be output directly to the page as text.

Common Solutions:

  • Navigate to the plugin's settings (GTM4WP > General Settings).
  • Change the Container code placement option. Experiment with different settings like 'Codeless' or 'Off' for the noscript part to see which one resolves the issue for your theme.
  • In your Google Tag Manager container, review all Custom HTML tags. Ensure every piece of JavaScript code is properly contained within <script> tags.

2. PHP Notices and Warnings in Logs or Admin

The Problem: Notices such as Undefined index, Trying to access array offset on value of type null, or A non-numeric value encountered appear in error logs or the WordPress admin area. These are often related to the WooCommerce integration file (woocommerce.php).

Why it Happens: These are not fatal errors but indicate that the code is trying to access a variable or array element that does not exist or is null. This can occur during specific edge cases, like REST API calls, or if certain WooCommerce data (like a product category) is unexpectedly missing.

Common Solutions:

  • Update the Plugin: The GTM4WP team is typically very responsive to these notices and releases fixes quickly. Ensure you are running the latest version of the plugin, as many of these notices have been patched in past updates.
  • Check for Data Consistency: If the notice is related to product data (e.g., line 969 or 873 in woocommerce.php), verify that your products have all necessary data assigned, such as categories.

3. Fatal Errors and Conflicts

The Problem: A PHP fatal error, such as Call to a member function get_applied_coupons() on null, causes a white screen or a critical error on the site, often on checkout or order-received pages. Conflicts with other plugins (like gift card plugins) are also common.

Why it Happens: These errors occur when the code expects a WordPress object (like the WooCommerce cart or order) to be present, but it is null. This can happen during non-standard requests, such as calls to the WP REST API or payment gateway callbacks, where the standard WooCommerce session is not fully loaded.

Common Solutions:

  • Update the Plugin: This is the most crucial step. Major refactoring of the plugin has happened in the past, and subsequent updates have included safety checks (like if ( null === $cart ) { return; }) to prevent these fatal errors. The fix for a specific error is often already committed to the GitHub repository and released in a subsequent version.
  • Check for a Fix: Search the plugin's official support forum or GitHub repository for the specific error message. It is highly likely that other users have already reported it, and a maintainer may have posted a code snippet or confirmed a fix is coming.

4. Performance Issues: 503 Errors and High Database Load

The Problem: The site becomes slow, times out, or returns HTTP 503 errors, especially on high-traffic pages like checkout. Database monitoring tools may show an unusually high number of INSERT/DELETE queries.

Why it Happens: This is frequently linked to the weather or geo-location data option within the plugin. When enabled, this feature uses WordPress transients, which involve storing temporary data in the database. On a busy WooCommerce site, the constant writing and expiration of these transients can cause significant database load.

Common Solutions:

  • Navigate to the plugin's settings (GTM4WP > Integration > Weather).
  • Disable the weather and geo-location data options unless they are absolutely necessary for your tracking setup.
  • Implement a persistent object cache (like Redis or Memcached) for your WordPress site. This dramatically reduces the load on the database by storing transients in memory.

5. Plugin Activation, Deletion, and Update Problems

The Problem: Users cannot activate the plugin due to a fatal error, or they cannot delete it through the WordPress admin because the deletion process itself triggers a critical error.

Why it Happens: A faulty update or a conflict during a specific WordPress version can cause these issues. The deletion process fails because it tries to run plugin code (which is causing the error) during uninstallation.

Common Solutions:

  • For Activation Errors: Check the error logs for the exact fatal error message. Often, a new version is released shortly after a major WordPress update to address compatibility.
  • For Deletion Errors: If the admin deletion fails, you have two options:
    1. Manually delete the plugin via FTP/SFTP by removing the duracelltomi-google-tag-manager directory from /wp-content/plugins/.
    2. To also remove the plugin's database options, you may need to manually delete the gtm4wp-options entry from your WordPress wp_options table using a tool like phpMyAdmin.

General Advice: When troubleshooting, always follow best practices: create a full backup of your site, test changes on a staging environment first, and enable WordPress debugging to get detailed error messages. The community around this plugin is active, so searching for your specific error message often leads to a known solution or workaround.

Related Support Threads Support