blog
Field notes
Every article here comes out of a real debugging session on a real store. Tracking rarely breaks loudly — it breaks quietly, keeps reporting numbers, and the numbers are wrong. These are the specific ways that happens.
Opening with these
TODO(owner): review before publishing — 3 articles written from the plugin
project files, waiting on your sign-off. They carry noindex and are
excluded from the sitemap and the RSS feed until you flip
status to published.
-
Draft — awaiting reviewHow page caching silently breaks your pixel
If a plugin writes the event ID into your HTML, the cache freezes one ID for everybody — and the platform folds thousands of conversions into one.
-
Draft — awaiting reviewProcessed vs Deduplicated in Meta Events Manager
The label that reads like a warning is the one you want. What Meta's two source labels actually mean, and the session trap that fakes a broken pixel.
-
Draft — awaiting reviewWhy purchases disappear when customers pay with PayPal
The thank-you page is the least reliable part of a checkout, and most plugins hang the Purchase event on it. Fire from the payment hook instead.
New articles go out on the RSS feed. Releases are on the changelog.
Reading about it is slower than checking.
Run the free Tracking Checker on your own store. It reads the page like a visitor and tells you what is actually there.