Title: EventLoomix – Data Layer for Google Tag Manager Author: nurulasad Published: September 12, 2026 Last modified: September 12, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/eventloomix-data-layer.svg) # EventLoomix – Data Layer for Google Tag Manager By [nurulasad](https://profiles.wordpress.org/nurulasad/) [Download](https://downloads.wordpress.org/plugin/eventloomix-data-layer.0.4.27.zip) * [Details](https://wordpress.org/plugins/eventloomix-data-layer/#description) * [Reviews](https://wordpress.org/plugins/eventloomix-data-layer/#reviews) * [Installation](https://wordpress.org/plugins/eventloomix-data-layer/#installation) * [Development](https://wordpress.org/plugins/eventloomix-data-layer/#developers) [Support](https://wordpress.org/support/plugin/eventloomix-data-layer/) ## Description EventLoomix – Data Layer for Google Tag Manager creates structured data-layer events from WordPress, WooCommerce and supported form-provider signals. It can use an existing GTM installation or install a configured GTM container after the administrator confirms that visitor consent has been configured. #### Ecommerce events * view_item and view_item_list * select_item * add_to_cart and remove_from_cart * view_cart and begin_checkout * add_shipping_info and add_payment_info * purchase with transaction and item data #### Form events * form_start after real visitor interaction * form_submit and generate_lead after confirmed success * Optional form_error and form_abandon * Individual controls for supported form providers * Optional original and SHA-256 hashed submitted fields #### Privacy and data handling Original submitted form data is disabled by default. SHA-256 field output can be enabled separately. Free-text message and textarea fields require a separate opt- in. Passwords, uploaded files, payment-card data, CVV, OTP, security tokens and CAPTCHA values are always excluded. When consent enforcement is enabled, personal form fields and purchase customer data require marketing consent. Product-list attribution storage requires statistics consent. The plugin supports WP Consent API signals and exposes `ATEGTMConsent.set({ statistics: true, marketing: true})` for consent platforms that need a direct integration. The plugin does not operate an external analytics service. It places configured events into the site’s browser data layer. The site owner controls GTM tags, third- party destinations, visitor consent and retention. Same-tab temporary form data expires within five minutes and is removed after confirmed submission. An optional built-in consent banner provides Accept all, Reject all and granular Analytics/Advertising choices. Choices are stored in a first-party cookie and can be changed later using the Privacy choices button. The banner communicates Google Consent Mode v2 signals and can interoperate with the WP Consent API. Site owners remain responsible for suitable wording, regional configuration and legal compliance. Google Tag Manager and Google Analytics are trademarks of Google LLC. This plugin is independently developed and is not affiliated with or endorsed by Google. ### External services This plugin can optionally load Google Tag Manager when an administrator selects the managed mode and supplies a Google Tag Manager container ID. In that mode, the visitor’s browser requests the GTM script or no-script iframe from `www.googletagmanager. com`. The request can disclose standard connection information such as the visitor’s IP address, browser user agent, referring page and the configured container ID to Google. Tags configured by the site owner inside that container may send additional data to services chosen by the site owner. The plugin does not control those tags. No Google Tag Manager request is made by this plugin in Data Layer only, Test, or Disabled mode. Site administrators are responsible for configuring consent and the tags in their container before enabling managed mode. Google provides this service. See the [Google Tag Manager Terms of Service](https://www.google.com/analytics/terms/tag-manager/) and [Google Privacy Policy](https://policies.google.com/privacy). ### Source code All JavaScript distributed in this plugin is the human-readable, directly editable source. No minified production bundle or build step is used. The files in `assets/ js/` are loaded directly by WordPress. Do not enable two WooCommerce ecommerce data-layer generators at the same time. If GTM4WP or a similar plugin generates ecommerce events, disable ecommerce in one plugin. ## Installation 1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin. 2. Activate EventLoomix – Data Layer for Google Tag Manager. 3. Open EventLoomix in WordPress Admin. 4. Select Data Layer only when GTM already exists, or Plugin manages GTM to enter a container ID. 5. Before using managed GTM, configure visitor consent and confirm the acknowledgement in settings. 6. Enable only the ecommerce and form providers required by the site. 7. Verify events in GTM Preview before publishing tags. ## FAQ ### Does the plugin send data to its own server? No. The plugin does not provide or contact an external analytics collection service. In managed mode it loads the administrator-selected Google Tag Manager container. ### Can it work with an existing GTM installation? Yes. Select Data Layer only mode so the plugin does not install a second GTM container. ### Why are original form fields disabled by default? Form fields can contain personal information. Enable only the fields required for a documented analytics purpose and configure visitor consent before tags collect them. ### Are hashes anonymous data? Not necessarily. SHA-256 hashing does not automatically make personal data anonymous. Site owners remain responsible for consent, disclosure and destination configuration. ### Why are password and payment fields missing? They are intentionally excluded and cannot be enabled. ### Which forms are supported? The plugin includes adapters for Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Forms, Ninja Forms, Formidable Forms, JetFormBuilder, Everest Forms, HappyForms, Divi, Bricks, HubSpot, Mailchimp for WordPress, Klaviyo, Forminator, WS Form and standard HTML forms. Provider behavior can vary by version and configuration, so verify the exact form in GTM Preview. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “EventLoomix – Data Layer for Google Tag Manager” is open source software. The following people have contributed to this plugin. Contributors * [ nurulasad ](https://profiles.wordpress.org/nurulasad/) [Translate “EventLoomix – Data Layer for Google Tag Manager” into your language.](https://translate.wordpress.org/projects/wp-plugins/eventloomix-data-layer) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/eventloomix-data-layer/), check out the [SVN repository](https://plugins.svn.wordpress.org/eventloomix-data-layer/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/eventloomix-data-layer/) by [RSS](https://plugins.trac.wordpress.org/log/eventloomix-data-layer/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.4.27 * Clears the full ready-event manifest from GTM’s merged data model before later events use the compact EventLoomix identity. #### 0.4.26 * Sends the complete EventLoomix schema manifest only with `ate_data_layer_ready`. * Uses a compact product, version and schema identity on ecommerce and form events. #### 0.4.25 * Uses the WordPress core input sanitizer for the WooCommerce order-received key so automated security scanners can verify the existing validation path. #### 0.4.24 * Renamed the plugin to EventLoomix – Data Layer for Google Tag Manager and aligned the directory slug, text domain, translation template and public schema identity. * Aligned plugin ownership metadata with the submitting WordPress.org account. * Moved the settings-page JavaScript to an enqueued, human-readable source file. * Replaced manually printed form-completion script markup with the WordPress inline- script API. * Documented the optional Google Tag Manager external service, transmitted connection data, conditions of use, terms and privacy policy. * Documented that the distributed JavaScript files are directly editable source and require no build step. #### 0.4.23 * Added a verified order-received page fallback for purchase events when a checkout integration does not run the standard thank-you hook reliably. * Flushes late thank-you purchase events immediately instead of relying only on the page footer. * Prevents the fallback and WooCommerce hook from queuing the same purchase twice in one request. #### 0.4.22 * Excluded Google Tag Assistant and GTM debugger traffic from acquisition attribution. * Removed GTM preview parameters from stored landing-page URLs. * Prevented direct/debug-only visits from permanently locking first-touch or last- touch attribution. * Migrates previously stored debugger touches automatically during the next page view. #### 0.4.21 * Added consent-aware first-touch, session-touch and last-touch acquisition attribution. * Captures UTM parameters, supported advertising click IDs, external referrer, landing page and timestamp. * Adds attribution to EventLoomix ecommerce and form lifecycle events and provides configurable retention. #### 0.4.20 * Added a privacy-safe EventLoomix schema bridge for compatible browser tools. * Exposes configured event names, enabled capabilities and standard data-layer paths without personal data. * Adds bridge metadata to server, WooCommerce browser and form events. #### 0.4.19 * Renamed the plugin to EventLoomix – Data Layer for Google Tag Manager before its initial directory submission. * Aligned the plugin folder, main file, text domain, translation template and public documentation with the new `eventloomix-data-layer` slug. * Preserved existing internal settings, cookies and event metadata for upgrade compatibility. #### 0.4.18 * Made list-attribution cookie sanitization explicit and compatible with WordPress Plugin Check analysis. * Completed the release-candidate version and package consistency audit. #### 0.4.17 * Replaced manually printed inline scripts with the WordPress inline-script API. * Sanitized list-attribution cookies and request-method input before use. * Replaced the Formidable Forms catalog database query with the provider API. * Removed read-only query-parameter nonce warnings and normalized administration source line endings. * Prefixed uninstall-scope variables for WordPress coding standards. #### 0.4.16 * Added a gettext POT template for community and local translations. * Made default visitor-facing consent banner text and controls translatable. * Kept the text domain aligned with the plugin slug for WordPress.org language packs. #### 0.4.15 * Added WordPress.org icon and banner assets in standard and high-resolution sizes. * Added public listing copy, a privacy-safe screenshot plan and asset-upload instructions. * Expanded the screenshot captions for setup, ecommerce, forms, consent and diagnostics. #### 0.4.14 * Added expanded automated release checks for setup, security, documentation and version consistency. #### 0.4.13 * Declared WooCommerce HPOS and Cart/Checkout Blocks compatibility. * Added a WordPress Site Health configuration test and clearer conflict detection. #### 0.4.12 * Added a responsive administration design for settings, setup and documentation pages. * Improved settings feedback and plugin action links. #### 0.4.11 * Added a guided first-activation setup wizard for GTM, ecommerce, forms and consent. * Added safe profiles for no consent ownership, third-party CMP signals and the built-in banner. #### 0.4.10 * Added an in-dashboard Help & Documentation page with setup and verification guidance. * Added offline guides for GTM, ecommerce, forms, consent/CMP, diagnostics, troubleshooting, privacy and security. * Documented event prefixes/suffixes, isolated diagnostic events and consent responsibilities. #### 0.4.9 * Escaped all untrusted event and provider names in the diagnostics interface. * Changed diagnostic events to isolated ategtm_test_* names so standard production triggers do not fire accidentally. * Added intended_event metadata to diagnostic payloads. * Completed nonce, capability, input sanitization, output escaping, transient and uninstall audits. * Updated WordPress compatibility and release metadata. #### 0.4.8 * Added an administrator-only live frontend diagnostics panel. * Added GTM, GA4, Meta Pixel, TikTok Pixel, data-layer, CMP and form detection. * Added event counts, rapid-duplicate detection and ecommerce payload validation. * Added clearly marked view-item and form-submit test events. * Added a downloadable privacy-safe JSON diagnostic report. #### 0.4.7 * Added banner position, theme, colors, overlay and editable button labels. * Added a Cookie Policy link, policy version renewal and keyboard focus containment. * Improved mobile and visible-focus styling. #### 0.4.6 * Added form-field allow and deny lists. * Added field renaming and separate raw/hashed field output modes. * Preserved permanent exclusions for passwords, payments, files, OTPs, tokens and CAPTCHA. #### 0.4.5 * Disabled built-in consent ownership by default while keeping third-party CMP detection available. * Separated third-party read-only consent signals from plugin-generated Google consent commands. * Prevented third-party CMP signals from writing the plugin consent cookie or changing CMP state. * Allowed normal tracking when no consent integration is configured. #### 0.4.4 * Added consent-source selection and third-party CMP adapters. * Added integrations for WP Consent API, Complianz, CookieYes, Cookiebot, OneTrust/ CookiePro and iubenda. * Added auto-detection mode, a documented custom-event bridge and configurable OneTrust groups. * Added duplicate consent-state suppression and CMP source events in the data layer. * Added an administrator warning when a known CMP and the built-in banner are both active. #### 0.4.3 * Added selectable Basic and Advanced Consent Mode implementations. * Added global defaults for all seven supported consent storage signals. * Added strict regional presets for EEA, UK, Switzerland, US, Canada, Australia and Bangladesh. * Added wait-for-update, ads-data-redaction and URL-passthrough controls. * Added consent-aware delayed loading for plugin-managed GTM in Basic mode. #### 0.4.2 * Added an optional first-party cookie consent banner. * Added Accept all, Reject all, Customize and change-preferences controls. * Persisted Analytics and Advertising choices and restored them before GTM loads. * Connected banner choices to Google Consent Mode v2 and WP Consent API. * Added editable banner title, message, privacy-policy URL and retention period. #### 0.4.1 * Added Google Consent Mode v2 denied defaults and consent updates. * Added WP Consent API registration and live consent-change support. * Added a public ATEGTMConsent API for custom consent platforms. * Blocked personal form and purchase data without marketing consent. * Blocked product-list attribution storage without statistics consent. #### 0.4.0 * Added canonical browser form resolution for Gravity Forms, Fluent Forms and Elementor Forms. * Preserved pending form identity when AJAX success replaces the original form DOM. * Improved provider-specific success and failure isolation. #### 0.3.9 * Added translation metadata and translated core administration strings. * Improved plugin-header and release consistency checks. * Added Plugin Check preparation safeguards. #### 0.3.8 * Contact Form 7 events now use the actual numeric form ID. * Contact Form 7 titles are resolved from the WordPress form catalog. * Browser and server completion paths share the same Contact Form 7 identity. #### 0.3.7 * Added meaningful home, page, search, related-product and cross-sell list names. * Limited product-list attribution to 30 minutes. * Rejected old, malformed and future-dated attribution records. #### 0.3.6 * Added managed-GTM consent acknowledgement. * Added WordPress privacy-policy suggested text. * Added a separate free-text/message field control, disabled by default. * Expanded uninstall cleanup for temporary form-completion records. * Rebuilt the directory readme for privacy and submission clarity. #### 0.3.5 * Improved same-page Ninja Forms AJAX detection. * Cleared prior provider form data before each new form event. #### 0.3.4 * Added optional submitted form fields and SHA-256 field output. * Added sensitive-field exclusions. #### 0.3.0 * Added server-confirmed form completion handoff and provider deduplication. #### 0.2.0 * Added provider-specific form tracking and settings sections. #### 0.1.0 * Initial development release with GTM, WooCommerce and data-layer support. ## Meta * Version **0.4.27** * Last updated **8 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.3 or higher ** * Tested up to **7.1** * PHP version ** 8.0 or higher ** * Tags * [analytics](https://wordpress.org/plugins/tags/analytics/)[data layer](https://wordpress.org/plugins/tags/data-layer/) [form tracking](https://wordpress.org/plugins/tags/form-tracking/)[google tag manager](https://wordpress.org/plugins/tags/google-tag-manager/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/eventloomix-data-layer/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/eventloomix-data-layer/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/eventloomix-data-layer/reviews/) ## Contributors * [ nurulasad ](https://profiles.wordpress.org/nurulasad/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/eventloomix-data-layer/)