Add Documentation on Fast Fetch expected ad response

[guiann]

This is a documentation update request.

What's the issue?

Fast fetch network implementation is unclear. Please see this request on stackoverflow with no answer: https://stackoverflow.com/questions/62267848/getting-started-with-amp-and-rtc-as-a-vendor

Tips on Rendering Bugs

When trying to implement an AMP RTC integration, we find the need to implement a Fast fetch adserver endpoint. Can you please develop this point ? Server to server ad serving is standardized using IAB's oRTB specifications. Is it what's expected here ?

Informations on Ad server requirements can be found here https://github.com/ampproject/amphtml/blob/master/ads/google/a4a/docs/Network-Impl-Guide.md#ad-server-requirements

Request, headers SSL ... but nothing on the expected response format.

[guiann]

Can anyone answer those questions please:

In order to add a demand source through RTC with amp-ad type doubleclick, should we add a vendor in "callout-vendor.js"? RTC doc is only mentioning targeting informations. Is it the same process for demand source? How does the ad network (doubleclic here) makes the difference?

With multiple demand source set in RTC, what's the arbitration process between those? Is it a waterfall ? Should pricing information appear in ad response (thus the idea of oRTB format).

Any answer would be much appreciated, thank you.

[powerivq]

RTC does not do bidding on the client side. What RTC allows is calling out to various targeting endpoints, and collects the responses and send it to the ad server. It would be the responsibility of the ad server to decide what to do with the targeting information, and execute header bidding.

AMP waits for all targeting callout responses and merge them. An example can be seen here: https://github.com/ampproject/amphtml/blob/master/extensions/amp-a4a/rtc-documentation.md#end-to-end-example

[guiann]

Thanks a lot for those answers!

So targeting data should have this format: "{"targeting": {"ages": "18-24", "g":["m", "f", "o"]}}"

How can demand sources can be plugged into a doubleclick integration? And how does fast fetch interact with this case? I guess doubleclick have allowed some ad response format instead of targeting informations? Do you know where to find details on this particular case?

Thanks a lot!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.