Google Tag Manager Data-Layer Plugins for Developers
A free plugin with several hundred thousand installations does the data collection that $199 dashboard plugins charge for. It builds a complete data layer from WordPress and WooCommerce, exposes author, category, post type and every e-commerce event, and hands the whole thing to a tag manager where you decide what happens next.
If you are comfortable in a tag manager, this article will save you a licence fee. It explains what a data layer is, compares the tag manager route against plugin-managed tracking honestly, and covers the two places this approach genuinely earns its complexity: e-commerce and consent.
Verified August 2026. Plugin capabilities change; confirm current behaviour against your requirements.
What a data layer is
A data layer is a structured object on the page containing facts about what is being viewed and what just happened. That is the entire concept, and it is described far more intimidatingly than it deserves.
Your site knows things your tracking does not: this is a post, by this author, in this category, published on this date; this visitor just added two of this product at this price to their cart. A data layer publishes those facts in a standard place. A tag manager reads them and forwards whatever each destination needs.
The reason plugins exist to build it is that assembling this by hand means writing PHP and JavaScript for every event and every attribute, keeping it correct through theme changes, and repeating the work for each destination. A plugin does it once, correctly, and keeps it current.
The payoff is separation. Your site publishes facts; your tag manager decides who receives them. Adding an advertising platform later becomes a container change rather than another plugin, which is the property that makes this scale.
The 6 options compared
1. GTM4WP
Free, mature, and the reference implementation for this approach.
It builds the container snippet and a comprehensive data layer covering post attributes, user state, form interactions and the full WooCommerce event set with product and order detail. That is the same data collection the $199.50 tier of the dashboard plugins provides, at no cost and with more control over exactly what is published. Its WooCommerce implementation is the reason most stores end up here: item lists, cart operations, checkout steps and purchase detail all arrive correctly formatted, which is a substantial amount of work to reproduce by hand. What it does not do is show you anything, so it is a collection tool rather than a reporting one, and that distinction is the whole trade.
- Price: Free
- Data layer depth: Comprehensive
- Best for: Anyone comfortable in a tag manager
- Watch out for: No reporting of any kind
2. Pixel Manager for WooCommerce
Store-focused tracking with the awkward parts handled, for shops where advertising performance is the point.
Where a general data layer plugin publishes facts and leaves the destinations to you, this is built around getting conversion data to advertising platforms accurately, including server-side sending, deduplication between browser and server events, and correct handling of refunds and order value. Those details matter a great deal when ad platforms are optimising bids on the data you send. Analytics events come along as part of the same implementation. Choose it over the general option when paid acquisition is the primary channel and you want the difficult parts solved rather than configured. Choose the general option when analytics is the primary consumer and you want maximum control.
- Price: Free tier plus paid
- Data layer depth: Store focused
- Best for: Stores optimising paid acquisition
- Watch out for: Advertising first, analytics second
3. PixelYourSite
The multi-platform pixel manager, popular with marketers who want several advertising destinations without a tag manager.
It handles multiple advertising platforms and analytics from one settings screen, which is genuinely simpler than learning a tag manager for somebody whose job is running campaigns rather than implementing tracking. Event configuration is done in WordPress, so there is no second interface to manage. The trade-off is that you are back to plugin-managed tracking, with the tracking logic living in your site rather than in a container: changes require site access, and the separation that makes the tag manager approach scale is absent. For a single site run by a marketer, that is often the right call. For an agency across many sites, the container model wins.
- Price: Free tier plus paid
- Data layer depth: Its own event model
- Best for: Marketers avoiding a tag manager
- Watch out for: Tracking logic lives in the site
4. Site Kit
The free official plugin, which can install a tag manager container and gives you reporting the collection tools do not.
Its role in this architecture is complementary rather than competing: let the data layer plugin publish facts and the container distribute them, and use this for the wp-admin dashboard so clients and colleagues have somewhere to look. It also brings search performance data, which no tracking plugin provides and which is more actionable than traffic numbers for most sites. The important configuration point is to ensure only one thing is installing the analytics tag. Running the official plugin’s tracking alongside a container that also fires analytics produces duplicated pageviews, and the resulting numbers look plausible rather than obviously broken.
- Price: Free
- Data layer depth: Not its job
- Best for: Reporting alongside a container setup
- Watch out for: Do not double-install the analytics tag
5. Dashboard plugins doing their own tracking
The alternative architecture, worth stating fairly. From $99.50, with e-commerce and dimensions at $199.50.
These configure tracking and reporting together, which for a site owner without technical help is a genuinely better experience than assembling three components. Nothing to learn, nothing to test, reports in wp-admin from day one. The limitations appear when a second destination arrives: an advertising platform typically means another plugin with its own event implementation, and now two systems send overlapping data with no shared definition of a conversion. That is where the container model pays back. If analytics is your only consumer and you value simplicity, a dashboard plugin is a reasonable purchase and this article does not apply to you.
- Price: From $99.50
- Data layer depth: Internal, not exposed
- Best for: Single destination, no technical help
- Watch out for: A second destination means a second plugin
6. Hand-built data layer
The option to know about and rarely choose.
Writing your own means total control over structure and naming, which matters if you are feeding a data warehouse with an established schema or have requirements no plugin anticipated. The cost is ongoing: every WooCommerce update, every theme change and every new event is your maintenance, and the failure mode is silent. A pragmatic middle path exists and is what most experienced implementations use: run the free data layer plugin for the standard events and add your own custom pushes for the handful of things it does not cover. That gives you maintained coverage of the hard parts and full control of the specific ones, without owning the whole surface.
- Price: Developer time, ongoing
- Data layer depth: Whatever you build
- Best for: Warehouse schemas and unusual requirements
- Watch out for: Silent breakage after updates
Comparison table
| Option | Price | Data layer | Reporting | Multiple destinations |
|---|---|---|---|---|
| GTM4WP | Free | Comprehensive | None | Yes, via container |
| Pixel Manager for WooCommerce | Free plus paid | Store focused | Limited | Yes, ad platforms |
| PixelYourSite | Free plus paid | Own model | Limited | Yes, in the plugin |
| Site Kit | Free | No | Yes | Container install only |
| Dashboard plugins | From $99.50 | Internal | Yes, detailed | No |
| Hand-built | Developer time | Yours | None | Yes |
Where this approach earns its complexity
The tag manager route is more setup than a dashboard plugin. Two situations make that worth it, and one operational discipline keeps it working.
- Multiple destinations from one implementation. Analytics, two advertising platforms and a heatmap tool all consuming the same events means one definition of a purchase rather than four, and no plugin per destination.
- Consent handled once, at the right layer. A container can hold every tag behind a consent signal, so one configuration governs everything rather than each plugin implementing its own interpretation of the banner.
- Changes without touching the site. Adding a conversion event becomes a container publish rather than a deployment, which across client sites is the difference between an afternoon and a week.
- Use the preview mode every time. Before publishing any container change, walk the site in preview and confirm each tag fires exactly once on exactly the right event. This is the discipline that prevents silent double-counting.
- Test the full purchase path after any store change. Checkout plugins, payment gateways and theme updates all break tracking quietly, and the first sign is a month of understated revenue.
- Document the container. Naming conventions, what each tag does and which trigger fires it. A container nobody understands is worse than a plugin, because at least a plugin has documentation.
On consent specifically, this is the strongest argument for the approach. Implementing consent signalling correctly across several tracking plugins is difficult and easy to get subtly wrong; implementing it once in a container, with your consent banner setting the signal, is a single configuration you can test and verify.
Frequently asked questions
Do I need a tag manager at all?
Not if analytics is your only destination and you have no technical help. It pays for itself the moment a second destination or a consent requirement appears.
Is a free data layer plugin as good as a $199 tier?
For data collection, yes and often better. What the licence buys is reporting inside WordPress, which the free route does not provide.
Can I run a data layer plugin and a dashboard plugin?
Yes, with only one of them installing the analytics tag. Two tags means duplicated pageviews, and the inflated numbers look plausible rather than obviously wrong.
Does a tag manager slow the site down?
The container itself is small; what you load through it is the cost. It also makes that cost visible and controllable, which is an advantage over scattered plugin scripts.
How do I verify events are firing correctly?
Use the container preview mode and walk the whole path, confirming each tag fires once on the right event. Repeat after any store or theme change.
Should an agency standardise on this?
Yes, if the team is comfortable with it. One container per client and one data layer implementation means tracking changes without deployments across every site.
The verdict
If you are comfortable in a tag manager, GTM4WP is free and does the collection a $199.50 tier charges for. Author, category, post type and the full WooCommerce event set, published once and distributed to whatever you configure.
Pair it with the free official plugin for reporting, taking care that only one of them installs the analytics tag, and you have a complete setup at no cost.
For stores where paid acquisition drives revenue, a store-focused tracking plugin handles server-side sending and deduplication better than a general data layer will.
And if none of this appeals, buy the dashboard plugin without guilt. A tag manager you do not understand is worse than a licence fee, and the container model earns its complexity only when there is more than one destination or a consent requirement to satisfy.
