[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$frM5LVu-a0exzC_ZuRA8p078glEaVgrY2gaL2se-DdVo":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"duracelltomi","Thomas Geiger","https:\u002F\u002Fprofiles.wordpress.org\u002Fduracelltomi\u002F",1,700000,98,612,78,"2026-04-03T19:23:06.429Z",[14],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":8,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":9,"vuln_count":35,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"duracelltomi-google-tag-manager","GTM4WP – A Google Tag Manager (GTM) plugin for WordPress","1.22.3","\u003Cp>Google Tag Manager (GTM) is Google’s free tool for everyone to manage and deploy analytics and marketing tags as well as other code snippets\u003Cbr \u002F>\nusing an intuitive web UI. To learn more about this tool, visit the \u003Ca href=\"https:\u002F\u002Fmarketingplatform.google.com\u002Fabout\u002Ftag-manager\u002F\" rel=\"nofollow ugc\">official website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>This plugin places the GTM container code snippets onto your WordPress website so that you do not need to add it manually.\u003Cbr \u002F>\nMultiple containers are also supported!\u003C\u002Fp>\n\u003Cp>The plugin complements your GTM setup by pushing page meta data and user information into the so called data layer.\u003Cbr \u002F>\nGoogle’s official help pages includes \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Ftag-platform\u002Ftag-manager\u002Fdatalayer#datalayer\" rel=\"nofollow ugc\">more details about the data layer\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>PHP 7.4 is required to use this plugin.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>GTM container code placement\u003C\u002Fh4>\n\u003Cp>The original GTM container code is divided into two parts:\u003C\u002Fp>\n\u003Cp>The first part is a javascript code snippet that is added to the \u003Ccode>\u003Chead>\u003C\u002Fcode> section of every page of the website.\u003Cbr \u002F>\nThis part is critical to enable all features of GTM, and this plugin helps to place this part\u003Cbr \u002F>\ncorrectly on your site.\u003C\u002Fp>\n\u003Cp>The second part is an iframe snippet that acts as a failsafe\u002Ffallback should users’ JavaScript be disabled.\u003Cbr \u002F>\nGoogle recommends – for best performance – to place this code snippet directly after the opening \u003Ccode>\u003Cbody>\u003C\u002Fcode> tag on each page.\u003C\u002Fp>\n\u003Cp>Albeit not ideal, it will work when placed lower in the code. This plugin provides a code placement option for the second code snippet.\u003C\u002Fp>\n\u003Cp>If your WordPress theme is compatible with the additions of WordPress 5.2 then this plugin will place this second code to the right place.\u003Cbr \u002F>\nUsers of the Genisis theme, GeneratePress theme, Elementor, Oxygen Builder and Beaver Builder Theme will also have this placed correctly.\u003Cbr \u002F>\nTo utilize this, set the compatibility mode in plugin options to off.\u003C\u002Fp>\n\u003Cp>All other users can place this second code snippet using a custom PHP code (“Manually coded” option) or select the so called “Footer” option to\u003Cbr \u002F>\nadd the code lower in the code (it is not the recommended way but will work)\u003C\u002Fp>\n\u003Ch4>Basic data included\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>post\u002Fpage titles\u003C\u002Fli>\n\u003Cli>post\u002Fpage dates\u003C\u002Fli>\n\u003Cli>post\u002Fpage category names\u003C\u002Fli>\n\u003Cli>post\u002Fpage tag names\u003C\u002Fli>\n\u003Cli>post\u002Fpage author ID and name\u003C\u002Fli>\n\u003Cli>post\u002Fpage ID\u003C\u002Fli>\n\u003Cli>post types\u003C\u002Fli>\n\u003Cli>post format\u003C\u002Fli>\n\u003Cli>post count on the current page + in the current category\u002Ftag\u002Ftaxonomy\u003C\u002Fli>\n\u003Cli>custom terms associated with any post type\u003C\u002Fli>\n\u003Cli>logged in status\u003C\u002Fli>\n\u003Cli>logged in user role\u003C\u002Fli>\n\u003Cli>logged in user ID (to track cross device behaviour in Google Analytics)\u003C\u002Fli>\n\u003Cli>logged in user email address (both unhashed and SHA256 hased values to be used with tracking)\u003C\u002Fli>\n\u003Cli>logger in user creation date\u003C\u002Fli>\n\u003Cli>site search data\u003C\u002Fli>\n\u003Cli>site name and id (for WordPress multisite instances)\u003C\u002Fli>\n\u003Cli>IP address of the visitor (please use the explicit consent of the visitor to utilize this)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Browser \u002F OS \u002F Device data\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>browser data (name, version, engine)\u003C\u002Fli>\n\u003Cli>OS data (name, version)\u003C\u002Fli>\n\u003Cli>device data (type, manufacturer, model)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Data is provided using the WhichBrowser library: http:\u002F\u002Fwhichbrowser.net\u002F\u003C\u002Fp>\n\u003Ch4>Weather data\u003C\u002Fh4>\n\u003Cp>(beta)\u003C\u002Fp>\n\u003Cp>Push data about users’ current weather conditions into the dataLayer. This can be used to generate weather-related\u003Cbr \u002F>\naudience\u002Fremarketing lists on ad platforms and allows for user segmentation in your web analytics solutions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>weather category (clouds, rain, snow, etc.)\u003C\u002Fli>\n\u003Cli>weather description: more detailed data\u003C\u002Fli>\n\u003Cli>temperature in Celsius or Fahrenheit\u003C\u002Fli>\n\u003Cli>air pressure\u003C\u002Fli>\n\u003Cli>wind speed and degrees\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Weather data is queried from Open Weather Map. Depending on your websites traffic, additional fees may apply:\u003Cbr \u002F>\nhttp:\u002F\u002Fopenweathermap.org\u002Fprice\u003C\u002Fp>\n\u003Cp>An (free) API key from OpenWeatherMap is required for this feature to work.\u003C\u002Fp>\n\u003Cp>ipstack.com is used to determine the site visitor’s location. A (free) API key from IPStack.com is required for this feature to work:\u003Cbr \u002F>\nhttps:\u002F\u002Fipstack.com\u002Fproduct\u003C\u002Fp>\n\u003Ch4>Media player events\u003C\u002Fh4>\n\u003Cp>(experimental)\u003C\u002Fp>\n\u003Cp>Track users’ interaction with any embedded media:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>YouTube\u003C\u002Fli>\n\u003Cli>Vimeo\u003C\u002Fli>\n\u003Cli>Soundcloud\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>DataLayer events can be chosen to fire upon media player load, media is being played, paused\u002Fstopped and optionally when\u003Cbr \u002F>\nthe user reaches 10, 20, 30, …, 90, 100% of the media duration.\u003C\u002Fp>\n\u003Cp>Tracking is supported for embedded media using the built-in oEmbed feature of WordPress as well as most other media plugins\u003Cbr \u002F>\nand copy\u002Fpasted codes. Players injected into the website after page load are not currently supported.\u003C\u002Fp>\n\u003Ch4>Scroll tracking\u003C\u002Fh4>\n\u003Cp>Fire tags based on how the visitor scrolls from the top to the bottom of a page.\u003Cbr \u002F>\nAn example would be to separate “readers” (who spend a specified amount of time on a page) from “scrollers”\u003Cbr \u002F>\n(who only scroll through within seconds). You can use these events to fire Analytics tags and\u002For remarketing\u002Fconversion tags\u003Cbr \u002F>\n(for micro conversions).\u003C\u002Fp>\n\u003Cp>Scroll tracking is based on the solution originally created by\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Nick Mihailovski\u003C\u002Fli>\n\u003Cli>Thomas Baekdal\u003C\u002Fli>\n\u003Cli>Avinash Kaushik\u003C\u002Fli>\n\u003Cli>Joost de Valk\u003C\u002Fli>\n\u003Cli>Eivind Savio\u003C\u002Fli>\n\u003Cli>Justin Cutroni\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Original script:\u003Cbr \u002F>\nhttp:\u002F\u002Fcutroni.com\u002Fblog\u002F2012\u002F02\u002F21\u002Fadvanced-content-tracking-with-google-analytics-part-1\u002F\u003C\u002Fp>\n\u003Ch4>Blacklist & Whitelist Tag Manager tags, triggers and variables\u003C\u002Fh4>\n\u003Cp>To increase website security, you have the option to white- and blacklist tags\u002Ftriggers\u002Fvariables.\u003Cbr \u002F>\nYou can prevent specific tags from firing or the use of certain variable types regardless of your GTM setup.\u003C\u002Fp>\n\u003Cp>If the Google account associated with your GTM account is being hacked, an attacker could easily\u003Cbr \u002F>\nexecute malware on your website without accessing its code on your hosting server. By blacklisting custom HTML tags\u003Cbr \u002F>\nand\u002For custom JavaScript variables you can secure the Tag Manager container.\u003C\u002Fp>\n\u003Ch4>Integration\u003C\u002Fh4>\n\u003Cp>Google Tag Manager for WordPress integrates with several popular plugins. More integration to come!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Contact Form 7: fire an event when a Contact Form 7 form was submitted with any result (mail sent, mail failed, spam detected, invalid input)\u003C\u002Fli>\n\u003Cli>WooCommerce:\n\u003Cul>\n\u003Cli>Implementation of \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Ftag-manager\u002Fecommerce-ga4\" rel=\"nofollow ugc\">GA4 E-commerce\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Does not support promotions since WooCommerce does not have such a feature (yet)\u003C\u002Fli>\n\u003Cli>Does not support refunds\u003C\u002Fli>\n\u003Cli>Compatibility with High Performance Order Storage (HPOS)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>AMP: load your AMP container on the AMP version of your pages\u003C\u002Fli>\n\u003Cli>Cookiebot: use automatic cookie blocking mode if needed\u003C\u002Fli>\n\u003Cli>Google Consent Mode v2: fire the “default” command with specific consent flags to integrat with non-certified Consent Management Platforms (CMPs) and plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Server side containers\u003C\u002Fh4>\n\u003Cp>If you are using a \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Ftag-manager\u002Fserverside\u002Fsend-data#update_the_gtmjs_source_domain\" rel=\"nofollow ugc\">server side container\u003C\u002Fa>\u003Cbr \u002F>\nyou can enter your custom domain name and custom path to load gtm.js from your there.\u003C\u002Fp>\n\u003Ch4>Exclude specific user roles from being tracked\u003C\u002Fh4>\n\u003Cp>You can set which user roles needs to be excluded from tracking when a user with that role visits the frontend. This will completely disable the container code for that user.\u003C\u002Fp>\n","Advanced tag management for WordPress with Google Tag Manager",13906369,90,154,"2025-12-15T14:45:00.000Z","6.9.4","3.4.0","7.4",[28,29,30,31,32],"google-ads","google-analytics","google-tag-manager","gtm","tag-manager","https:\u002F\u002Fgtm4wp.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fduracelltomi-google-tag-manager.1.22.3.zip",3,0,"2022-05-31 00:00:00","2026-03-15T15:16:48.613Z"]