WooCommerce tracking and Google Analytics for WordPress stores

Analytics loses orders that complete outside the standard thank-you page, orders placed while a visitor has declined consent, and orders where the event fires before the data layer is ready. WooCommerce counts all of them because it is the system taking the money.

Because two things are sending it: a tracking plugin and a Google Tag Manager tag, or two plugins that each think they own analytics. We pick one source per event and switch the other off rather than adding a third layer to referee them.

Not necessarily. A plugin is convenient and a container is flexible, and problems start when both are live at once. We work with whichever you already run and remove the overlap.

Yes. One container, the standard ecommerce data layer, and tags that read from it rather than from the page markup. Reading values off the rendered page is what breaks the next time the theme changes.

Tracking that depends on page markup breaks. Tracking that reads a data layer the store populates usually survives. We build the second kind, which is also why a theme change later is a smaller event.

The events are shared, so getting WooCommerce reporting correctly is what makes both platforms’ conversions correct. Platform-specific work beyond that is scoped on its own.

The standard package is built for transactional stores with a cart and an online checkout. A WordPress site that collects leads for an offline sale is a different kind of measurement problem, and we say so rather than fitting it to the wrong system.