Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPS-38: Sovrn adapter Fledge module integration #73

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

ikagotso
Copy link

@ikagotso ikagotso commented Apr 10, 2024

This is an attempt to do Sovrn Prebid.js adapter integration with prebid's Fledge (Protected Audience) Module.
We should send imp.ext.ae field, if fledge support is enabled.
Also we should return fledgeAuctionConfigs if we receive any.

Copy link

@sejanick sejanick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that really all we need to do for Fledge support? It seems pretty straightforward! Is there any context I should have in addition to this? If not, I'm happy to approve, as this seems good from what I understand.

Is there anyway we can possibly test this at all?

@ikagotso
Copy link
Author

Is that really all we need to do for Fledge support? It seems pretty straightforward! Is there any context I should have in addition to this? If not, I'm happy to approve, as this seems good from what I understand.

Is there anyway we can possibly test this at all?

As Prebid.js is concerned, our adapter's part in this seems somewhat straightforward, agreed. (Other adapters I've checked do similar stuff). You can take a look at this doc about fledge support (this is a small one : https://docs.prebid.org/dev-docs/modules/fledgeForGpt.html)
Short summary:
Prebid should notify Blackbird that an imp is Fledge-eligible. Blackbird in it's own should notify dsps about it and must be eligible to receive auctionconfigs. So surely Blackbird changes are going to follow this PR and I am working on that right now.
Our flow diagram could help clarify some of this: https://authcore.atlassian.net/wiki/spaces/~63dc3368491b20ef64b9ae39/pages/2693237735425/Protected+Audience+API

Please lemme know if you have any more questions.

@ikagotso
Copy link
Author

Is that really all we need to do for Fledge support? It seems pretty straightforward! Is there any context I should have in addition to this? If not, I'm happy to approve, as this seems good from what I understand.

Is there anyway we can possibly test this at all?

As for testing, I am not fully clarified on that yet.

@azaidisovrn
Copy link

@ikagotso, in the context of accessibility, how will the PAAPI tag have access to the returned bids and AuctionConfigs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants