Skip to content

Proof it still works

Coming to PixelCapi Pro

Will you find out when tracking silently dies?

Tracking does not usually break loudly. A cache plugin updates, a theme is replaced, a token is rotated, and events simply stop — with no error anywhere you would think to look. The Health Watchdog is designed to keep checking after setup day and tell you when the pattern changes, so the discovery is an alert rather than a bad month.

shipped today

The two failure modes already designed out

Watchdog is about noticing breakage. These two remove common causes of it in the first place.

Cache-proof architecture

No per-visitor event ID is baked into cacheable HTML, and byte-identical cached pages still produce unique matched pairs. That has been verified against LiteSpeed Cache and other common page caches, with a multi-layer REST cache bypass.

Verification that is allowed to say no

The Verify button states what it can and cannot confirm for each platform. Google’s endpoint cannot authenticate credentials without OAuth, so PixelCapi says exactly that rather than showing a green check that would pass no matter what.

the mechanism

What the Watchdog is designed to catch

Coming to PixelCapi Pro

Everything in this section describes intended behaviour, not shipped behaviour.

An alert, not a dashboard you have to remember to open

The failure that costs money is the one nobody notices. A watchdog is only useful if it speaks first.

Watchdog Purchase last seen 6d ago store still selling
Conflict second source firing Meta pixel duplicates rising

Designed output. This capability has not shipped, and these are not real rows.

TODO(owner: screenshot)

Health Watchdog alerts and the Conflict Scanner — available once the capability ships.

how it will work

Three steps, once it ships

  1. step 1

    A baseline is learned from your own store

    What normal looks like is different for every shop. The Watchdog is designed to learn your own event pattern rather than compare you to someone else’s.

  2. step 2

    Silence is treated as a signal

    A Purchase event type that has not fired in days, on a store that is still taking orders, is designed to raise an alert — not wait for you to open a dashboard.

  3. step 3

    The Conflict Scanner names the other source

    When a second plugin, a theme snippet or a tag manager container starts firing the same pixel, the scanner is designed to point at the conflicting source rather than just reporting duplicates.

documentation

Read the details

The reference pages for this, including the parts that are still being verified.

Questions people ask about this

Short answers. Anything we cannot confirm, we say so.

Is the Health Watchdog available today?

No. The Health Watchdog and the Conflict Scanner are in development and carry the roadmap badge everywhere they appear on this site. The cache-proof architecture and honest verification they build on are in the released plugin now.

My tracking broke after a cache plugin update. Does PixelCapi prevent that?

It removes the most common cause. Nothing per-visitor is stored in cacheable HTML, so a cached page cannot serve a stale event ID, and the REST layer is bypassed at multiple levels. Noticing other kinds of breakage automatically is what the Watchdog is designed to add.

How will I be told?

Alerting is part of the capability in development. Because it has not shipped, we are not describing delivery channels or thresholds yet — the changelog will carry the detail when it does.

What can I check myself in the meantime?

The Tracking Checker reads your public pages the way a visitor does and reports the pixels it finds, including the same platform ID appearing more than once. It is free and needs no signup.

Proof beats promises. Watch this land.

This capability is in development. Release notes go out on the changelog as each part ships.

Check your tracking — free Follow the changelog