Yeah true,and thanks for that. I unintentionally oversimplified.

I meant the 'page' (including the FB pixel JS on it) could read the pixel but the problem is of course the page is composed of resources from multiple domains and parties.

I'm pretty sure these days the default is just a JS ping to an endpoint, but the eponymous pixel exists under noscript tags for legacy support.