3 ms·
The likely process at play here is cutting out the middle man from ad placement. Before GDPR, a company would have likely contacted an ad agency to target the
by pacbard 8y ago
The likely process at play here is cutting out the middle man from ad placement.
Before GDPR, a company would have likely contacted an ad agency to target the population that reads the NYT. Ads would then be sold to a pool of websites that included the NYT. After GDPR, this is no longer possible as the individual websites have stopped sharing targeting information with the ad agency. The only solution available to the same company is then to buy directly from the NYT (and maybe a few other big websites) rather than “syndicate” the ads through the agency.
It would be interesting to know how ad placements changed pre/post GDPR and how the ad revenue distribution shifted across different websites.
- kijin 8y agoCutting out the middlemen and their asinine trackers might also help reduce the number of third-party scripts and random HTTP requests on the page. This will make the page load faster, especially on mobile. Which is known to help increase revenue.
- mschuster91 8y ago> This will make the page load faster, especially on mobile. Which is known to help increase revenue. Most ad loaders actually run async these days, cutting out middlemen/trackers doesn't help you for time-to-first-readable-content. Biggest culprit there are expensive assets like dozens of different fonts/variation combos, pre-roll video ads and uncompressed images.
- kijin 8y agoAd-infested pages often feel sluggish even after all the readable content has loaded. It feels like the page hasn't finished loading yet. After all, it takes CPU, RAM, and bandwidth to run scripts and load images in the background. The difference is especially noticeable on mobile, and it's even worse when the scripts trigger redraws or mess with the scrolling.