Whittfield Holmes

<p><strong>BrandMeetsCode DataLayer Tracker</strong> sends <strong>structured data</strong> to <code>window.dataLayer</code> so Google Tag Manager or your own tags can consume consistent events and page context.</p>
<p>By <strong>Whittfield Holmes</strong> at <strong><a href="https://brandmeetscode.com/" rel="nofollow ugc">Brand Meets Code</a></strong>. Listed on WordPress.org as <strong>BrandMeetsCode DataLayer Tracker</strong>; the wp-admin menu is <strong>DataLayer Tracker</strong>.</p>
<p>This plugin is <strong>fully functional</strong> with <strong>no license checks</strong>, <strong>no trial period</strong>, <strong>no usage quotas</strong>, and <strong>no disabled settings</strong> in wp-admin.</p>
<h4>Included features</h4>
<ul>
<li><strong>Page & content context</strong> — page type, IDs, title, URL, slug/path, categories/tags, referrer, <strong>UTM parameters</strong></li>
<li><strong>Visitor & device hints</strong> — resolution, timezone offset, browser language; optional cookie exposure rules</li>
<li><strong>Logged-in user context</strong> — role-style flags and optional <strong>hashed user id</strong> (modes you configure)</li>
<li><strong>Engagement</strong> — scroll depth (modes), scroll back up, focus/blur, time on page, <strong>active time</strong>, <strong>hover intent</strong>, <strong>video progress</strong>, default clicks; optional deeper click/field/section options where listed in Settings</li>
<li><strong>Forms</strong> — <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><strong>WooCommerce (when enabled)</strong> — browser <strong>GA4-style ecommerce</strong> events (view_item, add_to_cart, purchase, etc.) when WooCommerce is active</li>
<li><strong>Google Tag Manager</strong> — optional container <strong>snippet</strong> output from settings (you configure tags inside GTM)</li>
<li><strong>Consent-aware loading</strong> — delay until consent, CMP preference, TCF option, fallbacks</li>
<li><strong>Page URL filtering</strong> — regex exclude list</li>
<li><strong>Sessions</strong> — client-side session timeout/heartbeat options</li>
<li><strong>Debugging</strong> — console logging levels and admin <strong>debug overlay</strong> (core panels)</li>
<li><strong>Developer-friendly</strong> — hooks/filters; push custom <code>window.dataLayer</code> events from theme or other plugins</li>
</ul>
<h4>Consent Management</h4>
<p>Auto-detection and integration patterns vary by CMP; you remain responsible for correct legal configuration on your site.</p>
<h4>Google Tag Manager</h4>
<p>Optional <strong>snippet</strong> + consistent <strong>dataLayer</strong> pushes. Configure tags, triggers, and variables inside GTM.</p>
<h3>External Services</h3>
<h4>Google Tag Manager (optional — only when you configure a container ID)</h4>
<p>This plugin includes an optional feature to inject the Google Tag Manager container snippet on your site’s front end. This feature is <strong>disabled by default</strong> and only activates when you enter a GTM Container ID in the plugin settings and enable the snippet toggle.</p>
<p><strong>What it does:</strong> 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.</p>
<p><strong>What data is sent:</strong> 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.</p>
<p><strong>When it is sent:</strong> 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.</p>
<p><strong>Service provider:</strong> Google LLC</p>
<ul>
<li><strong>Terms of Service:</strong> <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></li>
<li><strong>Privacy Policy:</strong> <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
<li><strong>GTM documentation:</strong> <a href="https://marketingplatform.google.com/about/tag-manager/" rel="nofollow ugc">Google Tag Manager</a></li>
</ul>
<h4>WordPress Admin AJAX</h4>
<p>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.</p>
<p><strong>Important:</strong> 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.</p>
<h3>Privacy Policy</h3>
<p>BrandMeetsCode DataLayer Tracker may expose, depending entirely on which options you enable:</p>
<ul>
<li>Page URL, titles, and taxonomy-style context</li>
<li>Logged-in user fields you choose to surface, including optional <strong>hashed</strong> 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>
<p>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.</p>
<p>Data is exposed to the browser <code>dataLayer</code>; downstream tags decide what leaves the site.</p>
<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>
<p>Developed by <strong>Whittfield Holmes</strong> at <strong><a href="https://brandmeetscode.com/" rel="nofollow ugc">Brand Meets Code</a></strong>.</p>
<p>Special thanks to the WordPress community, beta testers, and all users who provide feedback and feature requests.</p>


BrandMeetsCode DataLayer Tracker

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

Ronald Huereca

Marco Pereirinha

Leon Hitchens

ruskinconsulting

<p>Integrate Google Tag Manager into your website.</p>
<p>The great thing about Google Tag Manager (GTM) is that you are able to gather most of your tracking scripts in one place. You can then fire these scripts whenever you want, specified by the rules you set up. This sounds great, right? Well it is.  The only problem is that sometimes it takes a bit of implementing to set these rules up. This implementation can either be setting a dataLayer variable in the dataLayer before the tag manager script is loaded, or pushing a HTML event handler with the variable “event” to the dataLayer when a button is clicked. The problem is that this isn’t always that easy to do when you don’t have the ability/access to add the code to your site.</p>
<p>This is where the Metronet Tag Manager plugin shines. It really unlocks the power of the dataLayer so you can easily set macros and firing rules on almost any element.</p>
<p>This plugin lets you:</p>
<ul>
<li>Easily add as many dataLayer variables on a per-post and per-page basis as you need.</li>
<li>The plugin already gives you six predefined dataLayer variables that you can change/remove or test the system with. These will be loaded on all pages and posts.</li>
<li>Set up separate dataLayer variables for pages that aren’t posts or pages (like archives etc).</li>
<li>Lets you easily add a HTML event handler to any content link with the GTM TinyMCE  button in the WYSIWYG.</li>
<li>Lets you add your own unique ID or a class to each content link with the GTM TinyMCE button in the WYSIWYG.</li>
</ul>
<p>Please note that for this plugin to work there is a slight customization that is needed. WordPress doesn’t let you load scripts straight after the opening  tag which is where the GTM script needs to be placed to work correctly. To fix this you need to add <code><?php do_action( 'body_open' ); ?></code> just after the <code><body></code> tag and that’s it.</p>
<blockquote>
<p>Note, if you are using WordPress 5.2. and up, contact your theme developer and ask them to insert <code><?php wp_body_open(); ?></code> just after the opening body tag of their theme. Here is some code to <a href="https://gist.github.com/ronalfy/6b7f43e70e644320aba67d1876a0aeff" rel="nofollow ugc">show the theme developer to make it compatible with Metronet Tag Manager</a>.</p>
</blockquote>
<p>Please let us know if you have any feature requests or if you have any issues with this plugin.</p>
<p>Below are a couple of resources you might find valuable if you are new to Google Tag Manager</p>
<p>Official Google Tag Manager website<br />
https://developers.google.com/tag-manager/</p>
<p>Tracking Google Analytics Events with Google Tag Manager<br />
http://moz.com/ugc/tracking-google-analytics-events-with-google-tag-manager</p>
<p>Make Analytics Better with Tag Management and a Data Layer<br />
http://cutroni.com/blog/2012/05/14/make-analytics-better-with-tag-management-and-a-data-layer/</p>
<h3>Filtering Variables</h3>
<p>If you choose to place variable values inside percentage signs (e.g., %replace_test%), you can filter these as necessary.</p>
<p>Here’s an example:</p>
<pre><code>add_filter( 'gtm_replace_test', 'gtm_replace_test', 10, 3 );
function gtm_replace_test( $total_match, $match, $post_id ) {
    return "replaced with content";
}
</code></pre>
<p>The filter name is <code>gtm_</code> with the suffix of <code>replace_test</code>, since that content is inbetween the percentage signs.</p>


Metronet Tag Manager

Simple, unobtrusive - great plugin. 

And whenver i see the name i always think
"If young metro don't trust you?"

This plugin is awesome

The plugin is helpful with installing Google Tag Manager. Works on WordPress multisite websites. The plugin is simple, straightforward, and more secure than a simple "insert headers or footers" plugin. 

Easily Add GTM to any Website

Integrate Google Tag Manager into  your website.

BrandMeetsCode DataLayer Tracker vs Metronet Tag Manager