triggering many network requests when interacting programmatic partners trusted servers

[omriariav]

We have a scenario where we work with programmatic partners to get demand via RTB for matched users.

The client will request each partner's trusted server using the Protected Audiences API. We can end up with many of these requests for one impression.

We are currently doing this activity in the backend before we return the ads/creatives to the client.

Going forward, we will move the bidding activity for this flow to the client increasing the chances of causing page performance issues due to many network calls. As you probably know, making these network calls and running logic in the client can block the main thread and cause JS execution challenges that can impact SEO (Core Web Vitals - FID/INP) and harm the UX.

Have you considered these aspects when migrating RTB-matched user flow in reaching out to trusted servers from the client?

[JensenPaul]

Omri, thank you for filing this issue. To help me better understand and respond to your concern, could you clarify a few things: when you say "we will move the bidding activity for this flow to the client", are you referring to moving to using the Protected Audience API? when you say "making these network calls and running logic in the client", are you referring to Protected Audience API's fetches of trustedBiddingSignalsURLs and execution of generateBid() scripts? when you say "RTB-matched user flow", are you referring to pre-existing bidding mechanisms based on cookie matched users?

[omriariav]

Hi, @JensenPaul, Thank you for your reply and for clarifying my questions.
The answer will be yes for all of your points. We're referring to the protected audiences usage via programmatic channels. So yes for the trustedBiddingSignalsURL and the execution of generateBid() as mentioned. We also trying to see how the matching user activity can be done in the new environment?