4 ms·
As others said the whole functionality can be implemented server side, and you can serve it as part of the HTML. Or simply reverse proxy it and put that in an
by pas 7y ago
As others said the whole functionality can be implemented server side, and you can serve it as part of the HTML.
Or simply reverse proxy it and put that in an IFRAME (or use JS and lazy load it into a DIV).
The current problem is that every ad engine tracks everything they touch. Instead of tracking how well a particular ad performs on a given site. (Of course ad engines try to show ads that are relevant to the profile they built up, but since the hit rate is extremely low, most of it is just noise. Which is very annoying.)
To solve the self-reporting trust issues make the sites report each impression separately with some proxied meta data. (Which is equivalent to always reverse proxy-ing.)
Which would be a bit slower than today (because most sites are not CDNes around the world, but most ad engines are), but who cares, the megabytes of shit downloaded and running on each site slows down UX more.