Whittfield Holmes

BrandMeetsCode DataLayer Tracker sends structured data to <code>window.dataLayer</code> so Google Tag Manager or your own tags can consume consistent events and page context.
By Whittfield Holmes at <a href="https://brandmeetscode.com/" rel="nofollow ugc">Brand Meets Code</a>. Listed on WordPress.org as BrandMeetsCode DataLayer Tracker; the wp-admin menu is DataLayer Tracker.
This plugin is fully functional with no license checks, no trial period, no usage quotas, and no disabled settings in wp-admin.
<h4>Included features</h4>
<ul>
<li>Page & content context — page type, IDs, title, URL, slug/path, categories/tags, referrer, UTM parameters</li>
<li>Visitor & device hints — resolution, timezone offset, browser language; optional cookie exposure rules</li>
<li>Logged-in user context — role-style flags and optional hashed user id (modes you configure)</li>
<li>Engagement — scroll depth (modes), scroll back up, focus/blur, time on page, active time, hover intent, video progress, default clicks; optional deeper click/field/section options where listed in Settings</li>
<li>Forms — <code>form_view</code>, <code>form_field_start</code>, <code>form_submit</code>, <code>form_error</code>, <code>form_abandon</code>; optional form-vendor shortcut mode</li>
<li>WooCommerce (when enabled) — browser GA4-style ecommerce events (view_item, add_to_cart, purchase, etc.) when WooCommerce is active</li>
<li>Google Tag Manager — optional container snippet output from settings (you configure tags inside GTM)</li>
<li>Consent-aware loading — delay until consent, CMP preference, TCF option, fallbacks</li>
<li>Page URL filtering — regex exclude list</li>
<li>Sessions — client-side session timeout/heartbeat options</li>
<li>Debugging — console logging levels and admin debug overlay (core panels)</li>
<li>Developer-friendly — hooks/filters; push custom <code>window.dataLayer</code> events from theme or other plugins</li>
</ul>
<h4>Consent Management</h4>
Auto-detection and integration patterns vary by CMP; you remain responsible for correct legal configuration on your site.
<h4>Google Tag Manager</h4>
Optional snippet + consistent dataLayer pushes. Configure tags, triggers, and variables inside GTM.
<h3>External Services</h3>
<h4>Google Tag Manager (optional — only when you configure a container ID)</h4>
This plugin includes an optional feature to inject the Google Tag Manager container snippet on your site’s front end. This feature is disabled by default and only activates when you enter a GTM Container ID in the plugin settings and enable the snippet toggle.
What it does: When enabled, the plugin outputs the standard GTM <code><script></code> and <code><noscript></code> tags that load <code>https://www.googletagmanager.com/gtm.js</code>. This causes the visitor’s browser to contact Google’s servers to load the GTM container.
What data is sent: When GTM loads, Google receives the visitor’s IP address, browser, and the URL being viewed — the same data sent by any website that loads GTM. No additional data is sent by this plugin beyond the standard GTM request. The plugin itself populates <code>window.dataLayer</code> in the browser; it is your GTM configuration that determines what analytics data leaves the site.
When it is sent: Only on front-end page loads when the visitor’s browser downloads the GTM script. If the consent-delay feature is enabled, the snippet is withheld until the visitor grants consent via your CMP.
Service provider: Google LLC
<ul>
<li>Terms of Service: <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></li>
<li>Privacy Policy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
<li>GTM documentation: <a href="https://marketingplatform.google.com/about/tag-manager/" rel="nofollow ugc">Google Tag Manager</a></li>
</ul>
<h4>WordPress Admin AJAX</h4>
All plugin settings saves, the setup wizard, and admin actions use WordPress’s built-in <code>admin-ajax.php</code> endpoint. All requests go to your own WordPress installation. No data is sent to external servers by these requests.
Important: You are responsible for ensuring that any third-party analytics services (GTM, GA4, etc.) you configure on your site comply with applicable data-protection laws (GDPR, CCPA, etc.) and that visitors are properly informed. This plugin provides consent-delay and CMP-detection functionality to help withhold scripts until consent is obtained, but legal compliance remains your responsibility.
<h3>Privacy Policy</h3>
BrandMeetsCode DataLayer Tracker may expose, depending entirely on which options you enable:
<ul>
<li>Page URL, titles, and taxonomy-style context</li>
<li>Logged-in user fields you choose to surface, including optional hashed identifiers</li>
<li>Engagement signals (scroll depth, timing, generic form interactions)</li>
<li>WooCommerce-related item data when ecommerce tracking is enabled</li>
<li>Structured event data pushed to <code>window.dataLayer</code> for use by analytics tools you configure</li>
</ul>
This plugin does not send data to any external server on your behalf. You are responsible for consent, disclosure, and lawful basis for any analytics tools you add to your site. The plugin does not replace legal or DPO review.
Data is exposed to the browser <code>dataLayer</code>; downstream tags decide what leaves the site.
<h3>Support</h3>
<h4>Documentation</h4>
<ul>
<li>Full Documentation: <a href="https://datalayer-tracker.com/knowledge-base" rel="nofollow ugc">https://datalayer-tracker.com/knowledge-base</a></li>
<li>Video Tutorials: <a href="https://youtube.com/@whittfieldholmes" rel="nofollow ugc">YouTube Channel</a></li>
</ul>
<h4>Community Support</h4>
<ul>
<li>Support Forum: <a href="https://wordpress.org/support/plugin/brandmeetscode-datalayer-tracker" rel="ugc">WordPress.org</a></li>
</ul>
<h3>Developer Hooks</h3>
<h4>Filters (examples)</h4>
<pre><code>add_filter(
 'brandatr_before_push',
 static function ( $event ) {
 $event['custom_field'] = 'value';

 return $event;
 }
);

add_filter(
 'brandatr_should_track_event',
 static function ( $should_track, $event_name ) {
 if ( 'unwanted_event' === $event_name ) {
 return false;
 }

 return $should_track;
 },
 10,
 2
);
</code></pre>
<h4>Actions</h4>
<pre><code>// Run code after consent granted
add_action('brandatr_consent_granted', function($consent_types) {
 // Your code here
});

// Run code after dataLayer push
add_action('brandatr_after_push', function($event) {
 // Your code here
});
</code></pre>
<h4>JavaScript API</h4>
<pre><code>// Push custom event
window.dataLayer.push({
 event: 'custom_event',
 custom_param: 'value'
});

// Get session context
const context = window.ADTSession?.getContext();

// Check consent
const hasConsent = window.hasConsent('analytics');<h3>Credits</h3>
</code></pre>
Developed by Whittfield Holmes at <a href="https://brandmeetscode.com/" rel="nofollow ugc">Brand Meets Code</a>.
Special thanks to the WordPress community, beta testers, and all users who provide feedback and feature requests.

BrandMeetsCode DataLayer Tracker

GTM-ready dataLayer: consent-aware events, engagement, admin debug overlay, optional WooCommerce. Fully free—no license keys or locked settings.

jeroenfrenken

AdPage Tagging is a simple to use solution for setting up Google Tag Manager Server Side.
Benefits of tagging: 
* Increase cookie lifetime (also on Safari 16.4). 
* First party tracking with custom domains. 
* Get more control over your data sent to GTM
External depencies: 
AdPage Tagging is using external depencies for providing the service. These files are all loaded through the domain you configure inside the plugin and Tagging dashboard. 
The files are used to provide our service inside of WordPress.
We are using the following external depencies: 
* /settings.js this file is used for detecting adblockers and for loading the GTM container. 
* /adex.js this file is used for detecting adblockers and for loading the GTM container. 
* /script.js this file is a proxy of the GTM web container script. This is used for loading the GTM container (Proxy to GTM). 
* /order_created this is a endpoint for sending order data to the GTM container (webhooks)
All scripts arebove are loaded from the domain you configure. When entering a domain that is used inside trytagging.com your requests will be proxied through our servers to Google Tag Manager. 
See below the terms of service for the external depencies.
Links to the services used: 
AdPage Tagging: https://trytagging.com 
Google Tag Manager: https://marketingplatform.google.com/about/tag-manager/
Terms of service: 
AdPage Tagging terms of service: https://www.adpage.io/general-terms-and-conditions-of-service 
Google Tag Manager terms of service: https://www.google.com/analytics/terms/tag-manager/
for any questions regarding the loading of external depencies please contact us at support@adpage.io
This plugin is not affiliated with Google Tag Manager or Google.

Tagging

AdPage Tagging is a simple to use solution for setting up Google Tag Manager Server Side.

BrandMeetsCode DataLayer Tracker vs Tagging