Explain me what is the use of tag manger plugins? How it is helps to our website?
Awaiting for your reply
]]>New hook (finally!) in WordPress 5.2, for adding scripts right after the opening <body> tag.
Please integrate into plugin:
add_action( 'wp_body_open', array( __CLASS__, 'print_noscript_tag' ) );
`
]]>Hi,
is there an option to hide the panel by default for each logging in?
We are facing the tracking issue since 5-6 months for https://raisondetrespas.com/.
We have analyzed in analytics that there is lot of increase in the direct traffic which actually as organic traffic
If user searches for “raison detre spas” in the Google and redirect to the website this traffic is counted as direct traffic.
After redirection if we check in the document.referrer variable value in the console section of chrome browser the result will be “https://www.raisondetrespas.com/” itself not the google.com. We are able to replicate this issue with chrome browser
We have recently removed some JavaScript redirections from the website but the issue is still exists.
Can some one help with the above to resolve the tracking issue?
Thank you!
]]>When enabling cloud fare the rocket loader for scripts, GTM is throwing the “jQuery” not found error message in console.
Reason for issue:
Rocket loading will load the combined scripts (All .js files) after the loading of HTML Dom and GTM is using the inline jQuery dependable scripts for datalayer handling.
Suggestion:
1. using core javascript instead of jQuery
2. output the datalayer related scripts into separate js file and using the script localization for passing the data.
Hi, everybody. I just updates this plugin to its latest version 1.7 and now my websites seems to give a 500 error respons on the front-end.
I am curious if there are more users that are experiencing the same thing. Thanks
]]>Warning Fixes should be done in /plugins/duracelltomi-google-tag-manager/integration/woocommerce.php
Warning:id was called incorrectly. Product properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_product’), WP_Hook->apply_filters, call_user_func_array, gtm4wp_woocommerce_cart_item_product_filter, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.
Fix: $product->id should be replaced with $product->get_id()
Warning: post was called incorrectly. Product properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_product’), WP_Hook->apply_filters, call_user_func_array, gtm4wp_woocommerce_cart_item_product_filter, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.
Fix: Wherever we have code: $product->post->post_title; we should add $post_title = get_the_title($product_id); above this code $product->post->post_title should be changed to $post_title
Warning: product_type was called incorrectly. Product properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_product’), WP_Hook->apply_filters, call_user_func_array, gtm4wp_woocommerce_cart_item_product_filter, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.
Fix:$product->product_type should be replaced with $product->get_type()
]]>Hello,
I’ve used your plugin more than 14 times on our clients here in the United Kingdom — an amazing plugin indeed!
But I am unable to verify through Google Tag Manager, because Google recognises that I am not using the code snippet they provided in the Install.
If possible, could this be sorted out please?
Kind regards,
Mic
]]>Plugin works great, but in case the site is using Cloudflare, with Rocket Loader functionality turned on, this will prevent GTM tag to be fired.
To prevent this from happening, all we need to do is replace
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
with
<script data-cfasync="false">(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
There are no filters before this it echoed, so can’t do it without editing the plugin file itself.
It would be a great addition to the plugin since a lot of people running WordPress sites are using Cloudflare as well.
]]>Hi,
I like the way you’ve added the support for Genesis and THA themes to output the no script code earlier, rather than in the footer.
Would you consider adding a custom google_tag_manager_noscript_tag action hook for this plugin so that custom themes could trigger it to fire earlier in a friendly way by adding the following below the body tag?
do_action( 'google_tag_manager_noscript_tag' );
Currently I guess I could use the unprefixed THA hook do_action( 'body_top' ) to trigger it but thought there may be a benefit in having a hook specifically for this plugin that would reduce the chance of triggering something unexpected if another plugin were to clash with the unprefixed body_top action?
Just a thought…
Ben ??
]]>I’m migrating my site to all SSL and I’m using the plugin really-simple-ssl
It has a feature where is scans my site and plugins to find potential SSL issues.
It found this issue in your plugin.
However it does appear to work ok with SSL
Just curious to know if you have ever encountered this issue?
]]>Puts the snippet in the wrong place rendering it unusable by google.
]]>I would like to use the custom container code in my child theme (based on Twenty Twelve as the parent). However, it is not clear which file in my child theme needs editing?
header.php?
Please let me know and I will be able to make the change.
Thanks,
Stephen
]]>Occasionally when using this plugin, Google Tag Assistant reports the following error for the site.
<script> tag must not be included in a <div>
This is pretty rare, and here is the process I go through
- Add Google Tag Manger plugin to my site and activate it
- Create a container in GTM
- Configure the plugin with the GTM ID
- Verify that everything is fine with the Google Tag Assistant
- Add tags to the GTM container, save and publish it
- Observe the above error in the site with the Google Tag Assistant
- Remove all tags from the GTM container, observe that the error persists
- Deactivate the plugin, observe the error go away
This doesn’t happen every time, but often enough that it’s sort of annoying. Any thoughts or ideas on what might be going on?
Does the GTM Container Snippet still needs to be installed on every page?
]]>