`, `

` tags. It may break your theme. There is also an option named "Codeless" which attempts to place the container code correctly without additional theme tweaks. It may or may not work, this is an experimental feature, use it accordingly. = Why can't this plugin insert the container snippet after the opening body tag automatically? = Currently WordPress has two 'commands' or 'hooks' that a programmer can use: one for the `` section and one for the bottom of ``. There is no way to inject any content after the opening `` tag without manually editing your template files. Fortunately some theme authors already resolved this so in some cases you do not need to edit your template. I suggest that try the Custom placement (easiest) and use Google Tag Assistant Chrome browser extension to check whether the container code is placed as expected. If it shows an error, go ahead and edit your theme manually. = Facebook like/share/send button events do not fire for me, why? = It is a Facebook limitation. Click event tracking is only available for html5/xfbml buttons. If you or your social plugin inserts the Facebook buttons using IFRAMEs (like Sociable), it is not possible to track likes. == Screenshots == 1. Admin panel 2. Basic settings 3. Events 4. Integration panel 5. Advanced settings 6. Scroll tracking == Changelog == = 1.9.2 = * Fixed: possible PHP warning if geo data or weather data feature is turned on = 1.9.1 = * Fixed: handle out of quota cases with ipstack queries properly * Fixed: proper YouTube tracking for WordPress sites and WordPress multisites installed in a subdirectory * Fixed: properly detect client IP address and also properly escape this data while using it * Fixed: WooCommerce checkout steps after page load did not include products in the cart * Fixed: checkout step events for payment mode and shipping type not always fired * Fixed: the CMD on Mac will be treated just like the Ctrl key on Windows while processing the product click event in the WooCommerce integration (thy for luzinis) * Fixed: add currencyCode to every ecommerce action in WooCommerce integration * Fixed: better WooCommere Quick View integration * Fixed: possible cross site scripting vulnerability if site search tracking was enabled due to not properly escaped referrer url tracking * Changed: code cleanup in WooCommerce integration = 1.9 = * Added: initial support for AMP plugin from Automattic (thx koconder for the contribution!) * Added: option to remove tax from revenue data on order received page of WooCommerce * Added: WooCommerce enhanced ecommerce datasets now include stock levels * Added: new productIsVariable data layer variable is set to 1 on variable WooCommerce product pages * Added: product impressions can now be split into multiple chunks to prevent data loss on large product category and site home pages (thx Tim Zook for the contribution!) * IMPORTANT! You will need to update your GTM setup, please read the new Step 9 section of the [setup tutorial page](https://gtm4wp.com/how-to-articles/how-to-setup-enhanced-ecommerce-tracking). * Added: you can now disable flagging of WooCommerce orders as being already tracked once. In same cases (with iDeal for example) you may need this to make purchase tracking to work. * Added: uninstalling the plugin will now remove configured plugin options from database * Added: new advanced plugin option: data layer variable visitorDoNotTrack will include 1 if the user has set the [do not track flag](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/DNT) in his/her browser * Added: new data layer event when a user has logged in on the frontend: gtm4wp.userLoggedIn * Added: new data layer event when a new user has registered on the frontend: gtm4wp.userRegistered * Added: new advanced plugin option: move data layer declaration and Google Tag Manager container as close as possible to the beginning of the HTML document * Added: better WP Rocket support * Updated: Full Google Optimize support. Now the plugin can load your Google Optimize container with the [recommended code placement](https://support.google.com/optimize/answer/7359264?hl=en) * Updated: moved most of the inline JavaScript codes into separate .js files which should help cache plugins to do their job much better when my plugin is active * Fixed: wrong ecomm_pagetype on product search result pages * Fixed: PHP notice in some cases when geo data was not loaded properly * Fixed / Added: freegeoip.net was rebranded to ipstack.com and an API key is needed now even for free usage. You can now add your API key so that weather data and geo data can be added into the data layer * Warning: some plugin features will be remove from v1.10, most of them can be tracked now using pure Google Tag Manager triggers: * Social actions * Outbound link click events * Download click events * Email click events * Warning: PHP 5.6 is now the minimum recommended version to use this plugin. I advise to move to PHP 7.x = 1.8.1 = * Added: new visitorIP data layer variable to support post-GDPR implementations where for example internal traffic exclusion has to be made inside the browser * Fixed: JavaScript error around the variable gtm4wp_use_sku_instead * Fixed: added _ as a valid character for gtm_auth GTM environment variable * Fixed: corrected typo - gtm4wp.checkoutStepE**E**C * Fixed: two strings were not recognized by WordPress Translate on the admin page * Fixed: some other plugins call found_variation event of WooCommerce without product variation data being included * Fixed: product name included variation name on order received page which broke GA product reports * Fixed: in some cases, no contact form 7 data was being passed to the gtm4wp.contactForm7Submitted event * Updated: added CDATA markup around container code for better DOM compatibility * Updated: removed 'SKU:' prefix text from classic ecommerce dimension as it broke some enhanced ecommerce reports = 1.8 = * Fixed: weather data tracking codes could result in fatal PHP error * Fixed: cart events did to fire while user pressed the Enter key in quantity fields * Fixed: contact form 7 changed some code which prevented successful form submission tracking * Changed: links to plugin website updated * Changed: gtm4wp.cf7formid data layer variable now includes the ID of the form in WordPress * Added: gtm4wp.cf7inputs includes data that has been filled in the form * Added: [WooCommerce compatibility headers](https://docs.woocommerce.com/document/create-a-plugin/#section-10) * Added: admin warning for WooCommerce 2.x users. This plugin will drop support for WooCommerce 2.x soon * Added: postFormat data layer variable on singular pages * Added: customer* data layer variables with stored billing and shipping data, total number of orders and total value of those orders (needs WooCommerce 3.x) * Added: geo* data layer variables to get country, city, lat-lon coordinates of the visitor * Added: visitorUsername data layer variable with the username of the logged in user * Added: more detailed checkout reporting for WooCommerce sites * Add gtm4wp.checkoutStepEEC to your Ecommerce Helper trigger * Change a typo: gtm4wp.checkoutOptionE**C**C => gtm4wp.checkoutOptionE**E**C * Added: option to include full product category path in enhanced ecommerce reporting (can cause performance issues on large sites!) * Added: initial support for [Google Tag Manager Environments](https://support.google.com/tagmanager/answer/6311518?hl=en) * Added: support for [WooCommerce Quick View plugin](https://woocommerce.com/products/woocommerce-quick-view/) * Updated: description of code placement options to clarify what this option does * Updated: cleanup of readme.txt, spelling and grammar improvements * Updated: bundled WhichBrowser lib v2.0.32 = 1.7.2 = * Fixed: in some cases, the remove item from cart link in a WooCommerce cart was not altered properly with additional tracking codes * Fixed: product categories were empty in the cart, on the checkout pages and on the order received page for product variations * Fixed: checkout option data included checkout step #1 if cart page was setup to be the first * Fixed: even more WooCommerce 3.x compatibility * Added: registration date of the logged in user can be added to the data layer * Updated: geoplugin.net has been replaced by freegeoip.net for weather tracking which has far better quota for free usage * Updated: AdWords dynamic remarketing data layer items on a WooCommerce product page will be shown for the root product as well on variable product pages * Updated: Selecting a product variation will include the price of the product in AdWords dynamic remarketing data layer items * Updated: minor code cleanup = 1.7.1 = * Fixed: PHP 5.3 compatible syntax in frontend.php * Fixed: PHP error using classic ecommerce with WooCommerce 2.6.x * Updated: Added data-cfasync='false' to all