3 ms·

I have only a basic understanding of online advertising. Is that really how AMP ads work? If they are pre-rendered before the user clicks the link, when does th

by kall 5y ago

I have only a basic understanding of online advertising. Is that really how AMP ads work? If they are pre-rendered before the user clicks the link, when does the auction happen? Does it do a speculative auction when you load the search results page? It so, that is an incredibly unfair advantage for google. Or do you just mean that all possible ad creatives are server-side-rendered, so to speak, and kept ready in a google cache? Edit: oh probably pre rendered by the user browser in the background. In that case any ad could still trigger it‘s impression with a viewport listener, if that‘s what google needed them to do.

lern_too_spel 5y ago
> In that case any ad could still trigger it‘s impression with a viewport listener, if that‘s what google needed them to do. With AMP, Google (and Microsoft and the other companies running AMP caches) can verify that the ad doesn't trigger an impression until viewed, which they need to do because they serve it themselves. https://developers.google.com/authorized-buyers/rtb/amp-ads https://developers.google.com/authorized-buyers/rtb/amp-ads > Does it do a speculative auction when you load the search results page? Yes. > It so, that is an incredibly unfair advantage for google. Why would it be? Anybody can participate in the auction.
- 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 ago
      No, 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.
- kall 5y ago
  It seems unfair because the only party that could possibly run an auction before you click the link is google.

by kall 5y ago

lern_too_spel 5y ago

> In that case any ad could still trigger it‘s impression with a viewport listener, if that‘s what google needed them to do. With AMP, Google (and Microsoft and the other companies running AMP caches) can verify that the ad doesn't trigger an impression until viewed, which they need to do because they serve it themselves. https://developers.google.com/authorized-buyers/rtb/amp-ads https://developers.google.com/authorized-buyers/rtb/amp-ads > Does it do a speculative auction when you load the search results page? Yes. > It so, that is an incredibly unfair advantage for google. Why would it be? Anybody can participate in the auction.

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 ago
    No, 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.
kall 5y ago
It seems unfair because the only party that could possibly run an auction before you click the link is google.