-
Notifications
You must be signed in to change notification settings - Fork 240
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
All outgoing HTTP requests should be visible in DevTools networks tab #778
Comments
Thank you for your patience. Starting from Chrome version 119.0.6025.0, you can expect all protected audience network requests to be displayed in the DevTools network tab. The main changes can be found here: |
Huge thanks to the Chrome team for this, this is an excellent improvement that has already paid huge dividends in our developer velocity. |
Thanks for the implementation. I checked in Chrome Canary. I can see FF reporting events and key/value server calls but the calls to |
Starting from Chrome version 120.0.6099.0, reporting should now be visible within the DevTools network tab. This change can be found here. |
Marking this as closed as I think all the Protected Audience server calls should be visible in the DevTools Network tab now. Feel free to reopen or file another issue if you have further concerns. |
For transparency all outgoing PA network requests (trusted server calls, bidding & scoring scripts) should be fully visible in the DevTools window in particular the Network tab. When PA API is fully rolled out it is generally the first thing users look at to be able to detect wrong behaviors like requests taking too long or too many outgoing requests.
Currently it is only visible in the Performance tab (which doesn't give the full view as one can't see HTTP headers for example) or via external Chrome extensions (which most users have not installed)
Related to ticket #499
The text was updated successfully, but these errors were encountered: