When working with this API, debugging locally is supported in Chrome via chrome://conversion-internals, and DevTools warnings are printed in the console to highlight developer mistakes.
But debugging this API at scale remains difficult, for example in case reports are dropped.
A public discussion on how to improve this is taking place
here. If you're in this mailing list, you're likely to have tried the API locally or in production via an origin trial. Your unique perspective on this can help shape an improved debugging experience!
➡️Please share any ideas, friction points, and thoughts you may have on debugging this API by commenting on this GitHub issue or opening a new one. - What are issues you've encountered with the API?
- What made it difficult to troubleshoot these issues?
- What would have helped you?
Thank you!