Critical Warning: Failed on All Core Function

  • jaurioldm17

    (@jaurioldm17)


    4 months ago

    I am writing this review to save other developers and site owners the immense amount of time I have just lost. I needed to implement standard GA4 e-commerce tracking on a professional WordPress/WooCommerce site. Based on its popularity and countless recommendations, I chose GTM4WP as the solution to generate the required dataLayer.

    Unfortunately, after days of intensive, professional-level debugging, I discovered that the plugin was completely non-functional in my specific—yet very common—environment.

    The plugin failed at its two most essential tasks:

    1. GTM Snippet Injection: The plugin’s most basic feature—injecting the GTM container script into the website’s <head> and <body>—did not work at all. The script was simply not present. I had to bypass this functionality entirely and inject the code manually using another method (Code Snippets) just to get our GTM container to load.
    2. E-commerce dataLayer Generation (The Deal-Breaker): This is the primary reason anyone uses this plugin. After successfully loading our GTM container manually, I ran a full test purchase. By analyzing the GTM debug mode and the site’s dataLayer object, I can confirm that GTM4WP completely failed to generate the purchase event and its corresponding ecommerce object on the WooCommerce order confirmation page. It produced absolutely nothing.

    My Technical Environment (Please read this before you install):
    To help others, here is the stack where the plugin failed. This is likely the source of the conflict:

    • CMS: WordPress
    • E-commerce: WooCommerce
    • Theme: Hello Elementor (using a child theme)
    • Page Builder: Elementor Pro
    • Key Detail: I am using Elementor Pro to customize the WooCommerce page templates, including the “Thank You” / “Order Received” page.

    Conclusion:

    My conclusion is that GTM4WP is fundamentally incompatible with themes or page builders that override default WooCommerce templates—a standard practice for virtually any custom-designed website today. Because it cannot handle this common scenario, the plugin proved to be entirely useless for my project.

    While it may work on simple sites with basic, unmodified themes, it is not a reliable solution for professional, customized builds. The time and effort wasted diagnosing this incompatibility were substantial. I cannot recommend this plugin and strongly advise users with a similar tech stack to seek a manual implementation from the start.

Viewing 1 replies (of 1 total)
  • César Gracián

    (@magogracian)

    2 months, 4 weeks ago

    Hello, I am having the same issue with the purchase event and I use the exact same stack that you describe. But I been using this plugin since a long time ago and it used to work fine. It seems to be a recent update that caused this incompatibility. Hopefully they can fix it soon because I really like this plugin.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.