MIQAS
By Ensign
2026-08-15 · 6 min read

WooCommerce: fully working, except the events that matter

Short answer: a vendor told a merchant their WooCommerce integration was fully working. After setup, page view, view content and purchase were firing. Add to cart and initiate checkout, the two events that build a qualified audience rather than just a visitor count, were completely missing, and his Meta Event Match Quality score dropped from 9.2 to around 8.3. The integration worked. The events that decide what your ad spend is worth did not arrive.

The complaint as it was posted

A store owner posted a detailed account. He had contacted a well-known attribution tool, told them plainly that he had no in-house developer and could not do any custom coding, and was assured the integration was fully working without needing any. After setup, he found the tool was only detecting page views, view content and purchases. Add to cart, initiate checkout and several other events were missing entirely.

He also noticed his match-quality score had dropped from 9.2 to around 8.3. When he raised it, the vendor’s team did not acknowledge a fault in their plugin and told him he needed to add custom scripts to his website, the exact thing he had told them from the start that he could not do.

A second practitioner described the same shape of problem more briefly: tracking tools that promise native WooCommerce support and then hand you custom scripts once something breaks.

Different details, same result: a promise of a ready-made connection, and a gap sitting exactly in the middle of the funnel.

Why it is specifically add to cart and checkout

Page view and purchase are endpoint events. They happen at a clear, fixed moment: the page opens, or the order completes. Add to cart and initiate checkout are mid-funnel events. They depend on the script knowing exactly which button was clicked and which page element was carrying the price and product at that instant.

That is precisely the part of a WooCommerce site that changes most often. A theme update, a caching plugin being switched on, or a page builder altering the structure of the cart element will change what a script is reading from, without touching checkout or payment at all. The final event keeps working because its path is simpler and more stable. The mid-funnel event breaks quietly, because it is tied to interface details that move more.

That is a description of how the WooCommerce and WordPress surface generally behaves, based on the platform’s mechanics, rather than a cause either merchant named directly. It explains how “the integration works” can be true and misleading at the same time.

What losing these two events actually costs

When add to cart and initiate checkout disappear, the algorithm loses its sharpest signal of near-purchase intent. It cannot learn from people who cared enough to act but did not buy, or from people who started paying and did not finish. It learns only from people who completed a purchase, which is a much narrower base for building a lookalike audience or a retargeting list.

Meta’s match-quality score reflects how complete the information attached to each event is. A drop from 9.2 to 8.3, as the owner reported it himself, means every event was arriving with less information, which reduces targeting accuracy across every remaining event, not only the two that went missing.

Where MIQAS comes in

The MIQAS pixel installs at the website level rather than as a plugin tied to one theme or page builder, so it reads the action itself, a click on the add-to-cart button or arrival at the checkout page, instead of reading an interface element that can shift with every update.

Completed orders connect through a direct WooCommerce webhook, so the purchase arrives from its source rather than from a browser guess, and is sent server to server to Meta, TikTok, Snapchat, Google and X, past ad blockers and iOS restrictions.

Maintaining that connection is part of the subscription. When WordPress or WooCommerce updates a theme or a plugin, checking that tracking still works is our job, not something you discover weeks later after budget has already gone toward an incomplete audience.

Check yours today

  • Open Events Manager in Meta and look at the events received in the last seven days.
  • Confirm at least four are present: page view, add to cart, initiate checkout, and purchase.
  • If add to cart or initiate checkout is entirely absent while purchase arrives regularly, the gap exists, regardless of what whoever installed your tracking told you.
  • Check the match-quality score per event. A noticeable drop means every event, even the ones working, is arriving with less information.

An integration that is “fully working” is a true sentence about three events, and an incomplete one about the two that decide what your ad spend is actually worth.

See it on your own data.

One dashboard that shows which ad drove every order; the live demo needs no card.

Related