Fledge module without GPT

[patmmccann]

Type of issue

Feature

Description

On #7634 (comment) it was clear there were two possible paths in the initial issue proposal, and Fledge for GPT was implemented. We still have publisher demand for Fledge without GPT as described by @JoelPM #7634 (comment)

[JoelPM]

This is an interesting topic. Just to make sure I understand completely, you are suggesting a use case for Prebid Fledge support when GAM is not the ad-server, is that correct? I'm not familiar enough with how Prebid functions in that case, but implementing a module for that use case should be doable.

If, however, you are referring to a use case where GAM is the ad server but does not run the Fledge auction, I don't think it's possible. When we first prototyped Fledge support GAM was not participating in Fledge auctions. That meant that if a Prebid participant won the auction, Prebid would know the value of the winning contextual bid and also had the opportunity to invoke runAdAuction (the Fledge auction) with that information. So even our prototype was limited to invoking Fledge only when a Prebid participant was the winner.

Now that GAM has decided to invoke runAdAuction via GPT after they receive their contextual response, there's no way for Prebid.js (or anyone else) to invoke the Fledge auction. Also, any attempt to invoke runAdAuction after GPT does would result in behavior that looks like fraud, as GAM/GPT will assume that it knows which ad won and rendered and running a second Fledge auction would have the potential of over-riding the ad that was served. It also wouldn't know what to use as a floor.

Of course, after typing that all up, I realized that javascript allows us to override navigator functions, which means you can do something like this:

const fledge = navigator.runAdAuction;

navigator.runAdAuction = function(auctionConfig) {
    console.log("runAdAuction called with AuctionConfig:");
    console.log(auctionConfig);

    return fledge(auctionConfig);
}

This is a giant hack. But it gives someone else the ability to run the Fledge auction, though it will likely cause reporting errors in GAM.

If someone wanted to see what this looked like in action they could go to this page and open up the developer console:
https://codinginadtech.com/prebid-live-tests/fledge/gptJoel.html?pbjs_debug=true

The results are fairly interesting.

[JoelPM]

This was discussed at the Prebid PMC meeting on 2/15/23. It sounds like the goal is to enable Prebid.js to manage the top-level Fledge Auction for publishers who aren't using GAM as the ad server. Given the evolving nature of Fledge and the limited testing happening right now I think it makes sense to revisit this later in Q2 '23.

[wojciech-bialy-wpm]

We are (as a publisher) looking into the same issue - i.e. executing top-level fledge auction outside GAM.

In test environment, we do it by emiting new CONSTANTS.EVENTS.FLEDGE_AUCTION event in onFledgeAuctionConfigs(), and storing incoming componentAuctions outside prebid.js.

But perhaps Prebid should expose getFledgeAuctionsForAdunitCode (or a similar) method?

[remysaissy]

This was discussed at the Prebid PMC meeting on 2/15/23. It sounds like the goal is to enable Prebid.js to manage the top-level Fledge Auction for publishers who aren't using GAM as the ad server. Given the evolving nature of Fledge and the limited testing happening right now I think it makes sense to revisit this later in Q2 '23.

Hello, we (Teads) are considering using Prebid without GPT for Fledge auctions. Hence I wonder what was the outcome of the revisit?

Thanks!

[patmmccann]

Closed as dupe of 10690