Why does Meta Pixel Helper only show PageView on WooCommerce?
If Meta Pixel Helper only shows PageView on your WooCommerce store, that does not usually mean your ecommerce tracking is broken. With PixelFlow, this is expected behavior in many WooCommerce setups because PageView is the browser-side page load event, while other WooCommerce ecommerce events are primarily sent server side through Meta’s Conversions API.
To confirm your setup is working, check How to Test and Verify Your PixelFlow CAPI Setup and review your PixelFlow event logs and Meta Events Manager.
Why this happens
PixelFlow uses both the Meta Pixel and the Conversions API. In PixelFlow’s tracking model, browser and server events can work together and be deduplicated when needed.
On WooCommerce, PageView is the event you should expect to see from the browser when a page loads. For ecommerce activity such as AddToCart, InitiateCheckout, and Purchase, PixelFlow’s WooCommerce tracking sends those events server side so Meta still receives the conversion data it needs.
This server-side approach is intentional. PixelFlow is built around Conversions API tracking because it is more reliable when browser-based tracking is limited by ad blockers, tracking prevention, or cookie restrictions. PixelFlow’s own site explains that sending data through a server-first flow helps recover conversions that Meta Pixel alone can miss.
Do ecommerce events need to fire in both the browser and server?
No. Events do not need to be sent from both places to be valid.
PixelFlow supports browser-side tracking and server-side tracking together, but WooCommerce ecommerce events do not need a matching browser event for Meta to use them. If the event is sent correctly through the Conversions API, Meta still receives the conversion data.
That is why seeing only PageView in Meta Pixel Helper does not mean your WooCommerce tracking is incomplete. The browser extension is only one part of the picture.
What WooCommerce events does PixelFlow track?
PixelFlow’s WooCommerce setup automatically tracks core commerce events including page views, add to cart, checkout, and purchase. You can review the setup steps in How to Set Up PixelFlow for WooCommerce.
If you are comparing browser tracking to ecommerce tracking, it also helps to understand the difference between PageView and ViewContent.
How to verify your tracking correctly
Open your PixelFlow dashboard and review the event logs.
Browse your live WooCommerce store and trigger a real ecommerce action, such as adding a product to cart or completing checkout.
Confirm the event appears in PixelFlow.
Check Meta Events Manager to confirm Meta is receiving the event.
These checks are more reliable than judging the setup from Meta Pixel Helper alone because PixelFlow also sends events server side.
When to troubleshoot further
If you do not see WooCommerce events in PixelFlow event logs or in Meta Events Manager, then there may be a setup issue worth troubleshooting. In that case, start with How to Test and Verify Your PixelFlow CAPI Setup and Why is Meta Events Manager showing a low event coverage rate?.
If PageView is showing but your commerce events are not appearing in PixelFlow or Meta after a real store action, recheck your WooCommerce setup and make sure Track WooCommerce eCommerce Events is enabled.