Index Exchange Header Bidding Debug

We recently updated our Prebid.js wrapper to a newer version, integrating several SSPs, including Index Exchange. Post-update, we've started observing persistent discrepancies in impression accounting specifically for Index Exchange demand.

Specifically, there's a significant delta between reported Index Exchange bids, as observed client-side via Prebid's debugger, and the actual impressions logged by our ad server for that same demand. It appears bid responses are being received successfully on the client, but their data isn't translating correctly downstream or being properly recognized by our ad server's targeting logic. This issue seems to occur post-bid reception but prior to the ad server call, suggesting a parsing or data propagation problem rather than a bid timeout.

I've already utilized standard browser developer tools and Prebid's built-in debugging extensively. My goal now is to delve deeper into the Index Exchange adapter's behavior and thoroughly verify the integrity of its bid response parsing. We need to enhance our bidstream analysis beyond the current scope.

• Are there specific Index Exchange diagnostic tools, endpoint parameters, or console commands that provide granular insight into bidstream data flow specifically from their adapter?
• What are the recommended best practices for tracing Index Exchange bid response data integrity from client-side receipt through to the ad server call, beyond basic Prebid.js debugging?
• Are there any known Index Exchange adapter nuances or common misconfigurations in Prebid.js that could lead to discrepancies between client-side bid data and ad server impression logs in such scenarios?