Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To set up e-commerce tracking in WordPress, connect your store to a Google Analytics 4 property, then implement GA4’s e-commerce events through a WooCommerce-compatible extension or a Google Tag Manager/data-layer setup. Installing a general Analytics tag alone does not record product views, carts, checkouts, or purchases.
What you need before tracking sales
- A Google Analytics 4 property and a web data stream for the store’s website.
- Access to WordPress, the store plugin, and—if used—Google Tag Manager.
- A confirmed checkout path: standard WooCommerce pages, Cart and Checkout blocks, a custom checkout, or an off-site payment flow.
- A consent-management platform whose state changes can be shared with the analytics integration.
The instructions below use WooCommerce because it has documented Google Analytics integrations. Other WordPress commerce plugins and custom checkout flows require their own compatible event implementation.
Choose one implementation route
| Route | Best for | Trade-offs |
|---|---|---|
| WooCommerce-aware analytics extension | Stores that want managed product, cart, checkout, and transaction events | Less implementation work, but compatibility and event coverage depend on the extension and its updates |
| Google Tag Manager with a correct data layer or event payload | Teams needing custom events, special checkout logic, or granular control | More flexible, but requires accurate item data, consent handling, and ongoing QA |
Use a single deliberate event implementation. If several plugins or tags send the same purchase, page view, or cart event, investigate possible duplication during testing rather than assuming every combination handles it safely.
How do I set up e-commerce tracking in WordPress?
-
Identify the store and checkout
Confirm whether the site uses WooCommerce or another commerce plugin. Document product, cart, checkout, payment, thank-you, and refund paths, including blocks, extensions, custom code, headless pages, and off-site payment providers.
-
Create or select the GA4 destination
In Google Analytics, choose the property and web data stream that should receive the store data. Record the stream’s measurement destination and use it consistently in the selected plugin or Tag Manager configuration.
-
Install one compatible implementation
Configure a WooCommerce-aware integration, or build the Tag Manager setup that reads the store’s data layer and sends GA4 events. Do not treat the base Google tag as a substitute for commerce events.
-
Map the shopping funnel
Implement only the events that match the store’s journey, using GA4’s exact names and parameter structure:
DriversOutdated Drivers Are Slowing You DownPerformancePC Slower Than It Used to Be?DriversCrashes, No Sound, or Screen Glitches?Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.view_item_listwhen a shopper sees a product listselect_itemwhen a shopper selects a product from a listview_itemon a product-detail viewadd_to_cartandremove_from_cartfor cart changesview_cartwhen the cart is displayedbegin_checkoutwhen checkout startsadd_shipping_infoandadd_payment_infowhen those details are submittedpurchaseafter a completed transactionrefundwhen refunds are represented in the implementation- Promotion events where the store needs to measure banners, coupons, or other promotions
Send an
itemsarray with the product information available to the store, such as item ID, item name, and price. When sending revenuevalue, include the transactioncurrencyat event level so GA4 can interpret the amount correctly. -
Connect consent behavior
Consent choices can determine whether analytics data is sent. WooCommerce’s documented integration relies on consent-state updates after visitors grant permission and points to compatible consent-management platforms using the WordPress Consent API. Configure the consent plugin and analytics route together, then verify that the state changes reach the tags or integration in each region you serve.
-
Test before relying on reports
Use a staging site when possible; otherwise run a controlled visit and representative test order. Enable GA4 debug mode and use Tag Assistant to check that the intended property receives the intended events, item parameters, currency, value, and transaction ID. Check that a purchase is not emitted merely by reloading a confirmation page or by a duplicate callback.
-
Compare analytics with store orders
After testing, compare recorded transactions and revenue with the store’s order records. This catches missing payment returns, failed callbacks, currency mismatches, and consent-related gaps that a successful browser test can miss.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
How do I track WooCommerce sales in Google Analytics 4?
Use a WooCommerce-aware Google Analytics integration or a Tag Manager implementation that sends a correctly structured purchase event after payment completion. The event should carry the transaction identifier, item details, revenue value, and currency available from the order. Include the earlier cart and checkout events if you need funnel abandonment analysis rather than sales totals alone.
Rank #3
WooCommerce extension considerations
WooCommerce documents a Google Analytics integration and a Pro extension with broader e-commerce event examples. Its documentation states that the extension supports GA4 and is compatible with Cart and Checkout blocks from WooCommerce 8.3; verify the current extension documentation against the versions running on your site before deployment. A paid extension is not required for every store, especially when an existing implementation already supplies reliable events.
Custom or off-site checkout considerations
If payment occurs on a hosted page, in a headless front end, or through custom callbacks, make sure the final transaction event can be attributed to the original session and is sent exactly once. The store plugin or payment provider may require a dedicated integration; a standard WordPress page-view tag cannot fill that gap.
Does Site Kit track WooCommerce purchases?
Site Kit can connect Google Analytics and Google Tag Manager and display metrics in the WordPress dashboard, but Site Kit alone cannot configure event tracking. Set up GA4 and/or Tag Manager events separately, and use a WooCommerce-aware integration or custom data implementation to provide product and transaction details.
Recommended Free Tools
How do I know GA4 is recording add-to-cart and purchase events?
- Open the site in a controlled test session with GA4 debug mode enabled.
- View a product, add it to the cart, begin checkout, and complete the representative purchase path.
- In Tag Assistant and GA4’s debugging views, confirm the event names, item data, currency, value, and transaction identifier.
- Repeat the confirmation-page reload test and check that it does not create another purchase.
- Compare the resulting transaction with the corresponding WooCommerce order.
Normal reporting is delayed. Google’s guidance describes a typical 24 to 48 hours before e-commerce data appears after users begin using a tagged site, while WooCommerce’s Pro documentation says configured event data can appear within 24 hours. These are expected time frames, not guarantees; use real-time and debug tools for implementation checks.
Common setup failures and fixes
Only page views appear
The base Analytics tag is present, but commerce events were never implemented. Add the WooCommerce event integration or the required Tag Manager/data-layer mappings.
Purchases are missing
Inspect the payment return and confirmation flow, especially for off-site gateways. Verify that the purchase event fires after a successful order and that consent permits the tag to run.
Revenue is wrong or shown in the wrong currency
Check that the order value is passed as the event’s value and that the matching ISO currency code is sent in currency. Confirm that item prices and discounts are mapped consistently with the store’s order total.
Events appear twice
Look for overlapping plugins, theme code, Tag Manager containers, and confirmation callbacks. Disable the redundant sender and retest the complete funnel, including confirmation-page reload behavior.
Block-based checkout behaves differently
Check the integration’s documented compatibility with the installed WooCommerce and block versions. If an extension does not support the active checkout, use a supported integration or implement the required events through the data layer.
Quick Recap
What to maintain after launch
- Retest products, carts, checkout, payment returns, refunds, promotions, and consent after theme, plugin, checkout, or payment changes.
- Review event parameters when product IDs, catalog fields, prices, taxes, discounts, or currencies change.
- Keep one owner responsible for the analytics integration and duplicate-event checks.
- Compare GA4 transactions with store orders periodically rather than treating a one-time test as permanent proof.
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.
