For most WooCommerce stores, the quickest route is WooCommerce’s Google Analytics integration: create a GA4 web data stream, copy its G- Measurement ID, paste it into WooCommerce > Settings > Integration > Google Analytics, enable the ecommerce events you need, and verify the hits with Google Tag Assistant. Your choice of payment gateway matters: the basic integration records a purchase when the shopper reaches the order-received (thank-you) page, while Pro or a server-side data-layer setup can cover payment flows that do not reliably return there.
Choose the tracking route before installing anything
Use the least complex implementation that covers your reporting and payment flow. These are WooCommerce’s documented routes:
![Google Workspace Guide: Unlock Every Google App – Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery [II EDITION]](https://m.media-amazon.com/images/I/41CX0AjJhAL._SL160_.jpg)
| Route | Best fit | Purchase trigger and event coverage | Complexity |
|---|---|---|---|
| Basic Google Analytics integration | A typical store that needs standard GA4 funnel events | Purchase tracking depends on the gateway returning the customer to the order-received page. Supports purchases, add/remove cart, product impressions and clicks, product-detail views, and checkout initiation. WooCommerce documentation | Lowest |
| WooCommerce Google Analytics Pro | Stores needing broader GA4 ecommerce and post-purchase events | Documents purchases, reviews, coupon use, full refunds, view-cart, begin-checkout, shipping and payment information, add/remove cart, and refund events. Its purchase tracking can use orders marked processing or completed instead of relying on the thank-you page. Pro documentation | Moderate |
| Google for WooCommerce | Stores creating Google Ads campaigns through the extension | Sets up campaign conversion actions such as purchases, page views, product pages, add-to-cart, and cart-page views when a campaign is created. FAQ | Moderate; avoid overlapping tags |
| DataLayer for WooCommerce with GTM | Implementers who need custom control or server-side delivery | Provides GA4 ecommerce events and can send purchase, order-pay, and refund events through a Google Tag Manager server container. DataLayer documentation | Highest; requires GTM configuration and, for server-side delivery, a server container |
Do not install several routes just to “improve” accuracy. Decide which system owns each conversion action, then disable duplicate Google Ads or analytics tracking where necessary.
Prerequisites
- A WordPress administrator account and a working WooCommerce store.
- A Google Analytics 4 property with a web data stream for the store’s domain.
- The stream’s Measurement ID, which starts with
G-. - Access to your payment gateway settings and a way to place a controlled test order.
- A consent-management solution if your store serves visitors in the EEA, UK, or Switzerland.
Set up the basic GA4 integration
- Create or select the GA4 property. In Google Analytics, create a GA4 property if you do not already have one, add a web data stream for the exact store domain, and copy its
G-Measurement ID. Google’s tag guidance is available in Google’s WooCommerce setup article. - Open the WooCommerce integration. In WordPress Admin, go to WooCommerce > Settings > Integration > Google Analytics.
- Enter the Measurement ID. Paste the
G-ID into the integration field. Check that it belongs to the web stream for this site, not another property or domain. - Enable the events your reports need. The documented basic options include purchase transactions, add-to-cart, remove-from-cart, product impressions, product clicks, product-detail views, and checkout initiation. Enable only the events you intend to analyze.
- Save and allow processing time. WooCommerce says the connection can take up to 48 hours to start working. Use real-time reports for immediate checks rather than judging the setup from standard reports alone.
Verify that events are actually being sent
WooCommerce recommends Google Tag Assistant for testing: “To test your analytics tracking and ensure it’s sending the correct data to Google, we recommend using the Google Tag Assistant website.”
Recommended Free Tools
- Open Google Tag Assistant and connect it to the storefront.
- Grant the site’s cookie consent when the banner appears; without consent, tracking may correctly remain inactive.
- In a new session, view a product, add it to the cart, remove it, and begin checkout. Complete a controlled test order if your gateway and test mode permit it.
- Inspect the Google tag’s Hits Sent view. Confirm that the actions you triggered produce hits and that the destination Measurement ID is the one you entered in WooCommerce.
- Check GA4’s real-time reports for the incoming activity. Normal ecommerce reports can take longer to populate.
Test as a normal shopper when possible. An administrator login, browser extensions, consent settings, or privacy blockers can change what your browser sends.
How purchase tracking depends on the payment gateway
In the basic integration, the purchase event is tied to the order-received (thank-you) page. If a gateway does not reliably redirect the shopper there after payment, an order can exist in WooCommerce without a corresponding GA4 purchase hit. WooCommerce lists WooPayments, Stripe, PayPal Braintree for WooCommerce, PayPal Payments, and Square as examples of gateways that perform this redirect.
Rank #2
![The Google Workspace Bible: [14 in 1] The Ultimate All-in-One Guide from Beginner to Advanced | Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite](https://m.media-amazon.com/images/I/41AWmhmGFuL._SL160_.jpg)
- The Google Workspace Bible: [14 in 1] The Ultimate All in One Guide from Beginner to Advanced Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite
- ABIS BOOK
If your payment flow can finish without that page, consider WooCommerce Google Analytics Pro, whose documentation describes purchase tracking for orders marked processing or completed, or use the data-layer/server-side route when you have the implementation expertise. Select based on the gateway behavior you actually operate, not merely on the presence of a successful order in the database.
Use Google Ads, GTM, or both without double-counting
Google for WooCommerce
Google for WooCommerce adds a Google Ads measurement layer. Its FAQ says that creating a campaign can create conversion actions for purchases, page views, product pages, add-to-cart, and cart-page views. This is useful when the extension is the system managing your campaigns.
Free tools Windows power users keep installed
One-click scans. No signup required.
Google Tag Manager
If GTM already sends Google Ads conversions, do not let Google for WooCommerce send the same action as well. WooCommerce documents a filter for disabling the extension’s Google Ads tracking; use it so one conversion has one deliberate owner. The same principle applies when a theme, another plugin, and GTM all inject Google tags.
Data-layer and server-side delivery
The DataLayer for WooCommerce extension is an advanced option for implementers who need custom event mapping or server-side delivery. It can expose GA4 ecommerce events and optionally send purchase, order-pay, and refund events through a GTM server container. A server container and event configuration are required, so this is not the default path for a simple store.
Consent, blockers, and why totals will differ
For the documented Google for WooCommerce setup, visitors in the EEA, UK, and Switzerland must grant cookie consent before analytics tracking activates. Google for WooCommerce does not provide the cookie-banner interface itself; it integrates with the WP Consent API, so a separate compatible consent extension must present the banner. See WooCommerce’s consent and campaign-analytics guidance.
GA4 and Google Ads are measurement systems, not an accounting ledger. Orders and analytics totals can diverge because of consent choices, ad and browser blockers, JavaScript errors, duplicate or missing tags, payment-return behavior, and the event trigger selected. Establish a baseline with controlled test orders and inspect the received event before using the reports for decisions.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTroubleshoot a missing or duplicate purchase
No events appear in Tag Assistant
- Confirm the
G-Measurement ID matches the active GA4 web stream. - Check that the integration is saved at WooCommerce > Settings > Integration > Google Analytics.
- Test in a non-administrator session and temporarily rule out browser extensions or content blockers.
- Open the browser console for JavaScript errors and remove unintended extra Google tags.
- Grant consent where the site requires it, then repeat the test.
Add-to-cart works but purchase does not
- Check whether the gateway returned the shopper to the order-received page; that return is required by the basic integration.
- Verify that the order reached the expected processing or completed state if you use Pro’s order-status-based purchase tracking.
- Inspect the payment flow and the final page in Tag Assistant rather than assuming that a paid order means a browser purchase hit was sent.
Conversions are higher than orders
- Look for the same Google Ads or GA4 conversion implemented by Google for WooCommerce, GTM, a theme, and another plugin.
- Choose one owner for each conversion action and disable overlapping tracking, including WooCommerce’s documented Google Ads filter when GTM is authoritative.
- Check whether refreshes or repeated visits to a thank-you page can retrigger the client-side event in your implementation.
Reports remain empty after a successful test
Allow the documented startup and processing window of up to 48 hours, while using GA4 real-time reports to confirm current traffic. If real-time is also empty, return to the tag, consent, gateway, and duplicate-code checks above.
A practical implementation decision
- Choose basic integration when you need standard funnel events and your gateway reliably redirects to the thank-you page.
- Choose Pro when refunds, coupons, reviews, shipping/payment steps, or payment flows that bypass that page are important.
- Choose Google for WooCommerce when its campaign workflow is your Google Ads system and you can prevent overlap with GTM.
- Choose DataLayer/GTM when you have an implementer who needs custom mappings or server-side event delivery.
Whichever route you select, document the event owner, the trigger, the Measurement ID, consent behavior, and the date of your controlled test. That record makes later debugging far faster than comparing unexplained totals.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
