Wire Pixel Test Harness

A set of intentionally lightweight Next.js pages, each loading the Wire tracking pixel a different way. Use them to confirm the race-condition theory in wire-pixel-implementation.md: if window.load fires before wire.js finishes downloading, the tracking pixel never fires.

Currently testing against account 79, property 6a2111320c2dee2dc5548935.

Scenarios

<script async> in <head>Likely FAILS
The "official" install. Reproduces the race condition on light pages — wire.js often arrives after window.load, listener never fires.
<script defer> in <head>Likely PASSES
Same placement, defer instead of async. defer guarantees execution before window.load, so the pixel should fire reliably.
<script async> appended to <body>Likely FAILS
Injected client-side after hydration — mirrors a tag-manager install.
next/script afterInteractiveUsually PASSES
Next.js default. Loaded after hydration but with a preload hint. Mirrors lektik.com/campaign.
next/script beforeInteractiveLikely PASSES
Injected into HTML before hydration. Closest to a hand-rolled tag.
next/script lazyOnloadAlways FAILS
Waits for idle AFTER window.load. Worst case — the load listener inside wire.js can never see the event.

How to read the dashboard

window.load fired — when the browser finished loading the page.
wire.js downloaded — when the wire.js script finished downloading. If this is later than window.load, the load listener inside wire.js misses the event.
Pixel request fired — when the actual /wire?token=… request to the Wire backend was made. This is the success signal. If this never lights up, the visit was not recorded.