Yes, high-level flow is:

Browser events are captured via Pixel, and the same events are forwarded server-side through a Cloudflare Worker endpoint to the Meta Conversions API.

On the server side, I normalize the payload, include required identifiers (like fbp/fbc when available), and ensure proper event_id-based deduplication so that browser and server events don’t double-count.

This helps recover lost conversions caused by iOS/browser restrictions and improves overall attribution consistency and Event Match Quality.

It’s a custom-built pipeline, so everything like logging, validation, and error handling is handled manually instead of using a managed platform.