You can learn what the user have read on the page before, and deliver more relevant ads next.
You can learn what the user have read on the page before, and deliver more relevant ads next.
> If scripting is disabled for img, return false.
> This is an anti-tracking measure, because if a user agent supported lazy loading when scripting is disabled, it would still be possible for a site to track a user's approximate scroll position throughout a session, by strategically placing images in a page's markup such that a server can track how many images are requested and when.
No, the change to the spec explicitly says lazy-loading is disabled if scripting is disabled just for this reason.
This has nothing to do with lazy-loading image tags. This browser-native functionality doesn't add any kind of new tracking, and pixels are never lazy-loaded anyway because they need to be fired as soon as possible to ensure data capture. Nothing about this new API changes anything for ads.
Lazy loading is entirely different and offers nothing new or useful for ads.
1. https://developer.mozilla.org/en-US/docs/Web/API/Intersectio...
Also in the last 5 years, every browser has added more functionality to block ads and tracking. Lazy loading is not going to somehow make up for that.
My question is what makes this better than the current script solution? Especially knowing this is intended to be built up with scripts.
My gut would also be a lot of folks think this will be good for tracking sure usage. On both sides of the fence.
I mean, I get what you mean: you place pixels strategically to see how far someone got on the page. But you can do that and more already (even full screen interaction) and no one uses that for ad targeting.