3 ms·
That’s not how it works at all. As you can see with the link you included, things like client IP address is sent along with the bid request. This happens after
by ec109685 5y ago
That’s not how it works at all. As you can see with the link you included, things like client IP address is sent along with the bid request. This happens after a user opens an amp article, not before.
The one second delay is so that ads that aren’t sandboxed and loaded client side, won’t impact the reading experience. For ads that are loaded server side, they can ensure the quality is high enough that they can be displayed while content is rendering.
- lern_too_spel 5y ago> The one second delay is so that ads that aren’t sandboxed and loaded client side, won’t impact the reading experience. Where does it say that? The delay is from the ad spot not even being available to bid on until the user opens the article, some timeout to receive all the bids, and then some time to fetch the ad from the winner's ad server instead of returning the ad content immediately after the winner has been determined. > For ads that are loaded server side, they can ensure the quality is high enough For ads that are loaded server side, they can just validate against the spec to ensure that it is safe for the AMP cache to serve inside the article.
- ec109685 5y agoNo, there is still a bid placed at render time for the amp ads — it can just be stitched in as soon as it’s ready since it is known to not to impact rendering performance.