Will this double-count against my existing pixels?

Not if you wire the shared event id. Each platform module sends the same id the browser pixel used, so the platform deduplicates the server event against the client one instead of counting both.

Starter repo manifest · Builder's Library

The Worker Fan-Out Starter

A copy-ready Cloudflare Worker that turns one form submit into clean, deduped conversions across every ad platform.

Unlock the kit

Client-side pixels lose a third of your conversions to ad blockers, ITP, and consent walls before the data ever reaches a platform. A server-side fan-out fixes that: the browser tells your Worker once, and the Worker tells every platform — from a network the blockers cannot reach. The cookbook makes the argument; this starter is the skeleton you deploy.

The hard part of a fan-out is not the first platform — it is the fifth, and keeping all five from double-counting the same lead. So the starter is built around one dedupe key shared across every platform, an audit row written to D1 for every attempt, and a module-per-platform layout that fails one platform without taking down the rest.

Free — one email

Unlock The Worker Fan-Out Starter.

Drop your email and the full kit opens right here — plus the next one when it ships. No drip sequence, no spam. Unsubscribe in one click.

Already unlocked on this device? The kit opens automatically.

This kit ships with the playbook it came from: Cloudflare Workers Fanout Cookbook — wrangler config, secrets, Logpush wiring for the 5-platform fanout.

Questions

Will this double-count against my existing pixels?: Not if you wire the shared event id. Each platform module sends the same id the browser pixel used, so the platform deduplicates the server event against the client one instead of counting both.

Want this built for you?

Skip the kit. We'll wire it.

20 minutes. Tell us what you're building, hear what we'd ship in the next 90 days. No pitch deck.

Book the call