loss notifications not getting triggered if no bids from component sellers make it to the top seller

[jlquaccia]

Hello,

While testing the PA auction flow, I had noticed a scenario where I am not seeing any loss notifications sent out if all bids are rejected during a PA auction. In fact when this occurs it looks like the reportWin and reportResult functions overall aren’t getting invoked? Additionally within our scoreAd function we are invoking reportAdAuctionLoss. To summarize, our expectation is that generateBid will return a bid, scoreAd gets called to score a bid, the bid gets rejected (invalid by some means within the ssp worklet), at this point we should get a loss notification in this case.

I also created a short video earlier illustrating this scenario further. Hope it helps!
https://vimeo.com/896691459?share=copy

[JensenPaul]

reportWin and reportResult are PA's event-level win reporting functions, so it's expected that they're not invoked if all bids are rejected during a PA auction, as there will be no winner.
As for why URLs passed to forDebuggingOnly.reportAdAuctionLoss() are not showing up in the DevTools Network panel, this was recently added to Chrome (see this comment) so it might be worth verifying this with a Canary or Dev channel build of Chrome. You could also collect a network log via chrome://net-export to verify that the requests are being made.
Please let me know if this problem persists. If you have a link to a site that reproduces this error, that would be helpful when debugging this issue.

[jlquaccia]

Hi @JensenPaul, thanks for looking into this. That makes sense for the expected outcome for reportWin and reportResult. For functionality around forDebuggingOnly.reportAdAuctionLoss(), I went back and tested the behavior out again within the following Chrome scenarios:

• Chome Canary (Version 123.0.6265.0 (Official Build) canary (arm64))
• Chrome Dev (Version 123.0.6262.5 (Official Build) dev (arm64))
• Chrome Beta (Version 122.0.6261.6 (Official Build) beta (arm64))
• Chrome (Version 121.0.6167.85 (Official Build) (arm64))

I also tested things out with the chrome://net-export tool you mentioned. When using the net export tool you mentioned I was able to see loss notification calls in the log file that the tool generates. However, when testing in the various scenarios above to see if loss notifications were visible within the chrome dev tools network tab, I still wasn't able to see anything.

To help make things easier for debugging, I created a quick demo page where 4 interest groups join and the ssp worklet intentionally rejects all of the generated bids (I added some details around this to print out in the dev console on the demo page). forDebuggingOnly.reportAdAuctionLoss is called and points to https://fledgelogger.pubmatic.com/AdServer/AdDisplayTrackerServlet, but no calls to that endpoint are visible in the network tab. Hopefully this demo helps! Let me know if you need anything else.

Demo page: https://owsdk-stagingams.pubmatic.com:8443/openwrap/TestPages/jason/publisher_pubmslot.html?pubmaticTest=true

[dmdabbs]

Hello @JensenPaul. Testing in Canary (125.0.6385.0) DevTools, Network still doesn't display forDebuggingOnly fetches, but they are issued and recorded in chrome://net-export. Not high prio if sampling is imminent.