Google Tag Manager install
Mimics how a tracking pixel installed through Google Tag Manager arrives on a page. GTM first loads its own container, then evaluates which tags to fire, then injects each individual tracking pixel. That whole sequence typically adds about 800ms on top of the normal page load — long enough that on most lightweight pages, window.load has already fired by the time wire.js shows up.
Each side runs the same scenario in its own iframe. The iframes load independently, so you can see how each pixel version behaves under identical conditions.
How to test:
- Load the page and wait ~4 seconds.
- Compare the order in the metrics row: window.load lands first, then wire.js downloads ~800ms later.
- Check the pixel column on each side.
Expected: V1 — pixel never fires. The GTM-style delivery delay means wire.js arrives after window.load every time. V2 — pixel fires on execute, regardless of timing.
V1 · current pixel
Verdict
Initialising…
window.load
—
wire.js
—
pixel
—
Event timeline
- No events recorded yet…
Script tag for this scenario
// Injected by a GTM-style container ~800ms after page load <script type="text/javascript" async src="https://staging-api.wire.spbx.app/wire.js?account_id=79&property_id=6a2111320c2dee2dc5548935"></script>
V2 · proposed fix
Verdict
Initialising…
window.load
—
wire.js
—
pixel
—
Event timeline
- No events recorded yet…
Script tag for this scenario
// Injected by a GTM-style container ~800ms after page load <script type="text/javascript" async src="https://staging-api.wire.spbx.app/wire.js?pixel_id=6a211df10c2dee2dc5548936&account_id=79&property_id=6a2111320c2dee2dc5548935"></script>