Home/Services/Ecommerce Tracking/WooCommerce Tracking
WooCommerce Tracking Set Up the Right Way
WooCommerce gives you full control over tracking, which also means plugins, caching and payment gateways can quietly break it. We build a dataLayer from WooCommerce hooks and connect it to GA4, Google Ads and Meta so product, cart and order events stay reliable.
WordPress stores on WooCommerce that run Google Ads or Meta campaigns
- Hook-based ecommerce dataLayer
- Classic and block checkout support
- Duplicate purchase protection
- GA4, Google Ads and Meta events via GTM
Free 30-minute tracking audit • No obligation
Why WooCommerce Tracking Breaks So Often
A typical WooCommerce site runs a theme, a page builder, caching, several tracking plugins and a payment gateway. Each one can change what the browser sees and when.
Plugin Overlap
Two or three tracking plugins each inject GA4 or Meta code. Events double up, and nobody is sure which plugin owns what.
Cached and AJAX Pages
Page caching serves stale product data, and AJAX add to cart buttons never reload the page, so events based on page loads miss them.
Gateway Redirects
Some payment gateways return shoppers to the order received page late or not at all, and a refresh of that page can resend the purchase.
What We Implement on WooCommerce
We work at the WooCommerce level, using its PHP hooks and order data, rather than scraping the page. That keeps tracking stable when the theme or page builder changes.
Hook-Based DataLayer
PHP functions on WooCommerce hooks push product, cart and order data in the GA4 ecommerce format.
AJAX Cart Event Handling
Listeners for WooCommerce cart fragments and block cart actions capture add_to_cart without a page reload.
Checkout Step Events
begin_checkout, add_shipping_info and add_payment_info for classic shortcode checkout or the block checkout.
Order Received Purchase
A purchase push on the order received page, flagged in order meta so a refresh never sends it twice.
GTM Tags for Each Platform
GA4, Google Ads conversion and Meta Pixel tags in GTM, all reading from the same dataLayer variables.
Cache and Plugin Configuration
Cache exclusions for cart and checkout, and removal or scoping of overlapping tracking plugins.
How WooCommerce Data Becomes Conversions
Data comes straight from WooCommerce objects on the server, is written to the dataLayer, and GTM sends one version of each event to every platform.
Product, cart or order object available
Event and items array in GA4 format
Triggers and variables per event
Platform tags fire with order data
Tracked orders checked in WooCommerce
What's Included in WooCommerce Tracking
Clear deliverables, documented and validated before handover.
WooCommerce Tracking Audit
A review of plugins, theme code, caching, checkout type and gateways to see what is firing and what conflicts.
Custom DataLayer Code
Lightweight PHP and JavaScript added through a child theme or small plugin, with no heavy tracking plugin dependency.
GTM Container Build
A structured container with named tags, triggers and variables for GA4, Google Ads and Meta.
Gateway and Checkout Testing
Test orders through each active payment method, including off-site gateways, with every event checked.
Implementation Notes
Documentation of the hooks used, where the code lives and what to recheck after WooCommerce updates.
Developer Handover
A walkthrough for your developer or agency so future site work does not undo the tracking.
From Audit to Validated Data
How a WooCommerce Tracking project runs, step by step.
Audit
Audit tracking plugins, caching, checkout type and payment gateways on the live store
Strategy
Plan the event map and decide which plugins stay, go or get scoped down
Implementation
Add hook-based dataLayer code and build GA4, Google Ads and Meta tags in GTM
Testing
Run test orders through every gateway, coupon path and cart interaction
Validation
Match tracked purchases to WooCommerce orders and hand over code and notes
Platforms and Tools We Work With
The tools involved in a typical WooCommerce Tracking implementation.
Hooks and order data
Child theme or plugin
Tags and triggers
Ecommerce events
Purchase conversion
Standard events
WooCommerce Tracking FAQ
Straight answers before you book. Still have a question? Talk to us directly.
Why not just use a WooCommerce tracking plugin?
Plugins can work, but they often add code you do not need, conflict with other plugins, or limit which parameters you can send. A small custom dataLayer gives you control and fewer moving parts. If a plugin fits your setup well, we will say so.
Does this work with the WooCommerce block checkout?
Yes. The block checkout behaves differently from the classic shortcode checkout, especially for checkout step events. We detect which one you use and build the events for it.
What about PayPal and other off-site gateways?
Off-site gateways can delay or skip the return to the order received page. We test each gateway you use. Where browser tracking is unreliable, we can add a server-side purchase event triggered by the order status change.
Will caching plugins interfere with tracking?
They can, mainly on cart and checkout pages or when product data is cached. We set cache exclusions where needed and make sure dynamic values are not served from a stale cached page.
Can this include server-side tracking?
Yes. WooCommerce order hooks can send purchases to a server-side GTM container or directly to Meta Conversions API. We add this after the browser layer is stable, with event IDs for deduplication.
Services That Work Well Together
Tracking is a system. These services are often delivered alongside this one.
A GA4-standard ecommerce dataLayer spec and build, so every tag reads the same product data.
A clean, well-named GTM container installed correctly with GA4, ads tags and consent in place.
Server container setup, hosting, custom subdomain and routing, ready for every platform.
Stop Guessing. Start Measuring.
Get a professional review of your tracking setup and discover where your marketing data may be leaking.
Free 30-minute review • No obligation