Debugging tools for data collection
Debugging tools, sometimes called packet analyzers or packet sniffers, let you inspect the data that your implementation sends to Adobe. This article helps you choose a tool. For how to use these tools to inspect requests and Edge Network processing, see Inspect data collection requests.
Choose a debugging tool choose-a-tool
The following categories can help you select a tool based on what you want to inspect.
Tag debuggers tag-debuggers
Tag debuggers recognize marketing and measurement technologies and interpret their requests. These tools can make it easier to identify Experience Platform Web SDK payloads, tags, data layers, and requests sent to Adobe applications or other vendors without manually decoding network requests.
Browser developer tools browser-developer-tools
Every modern browser includes developer tools that can inspect network requests, so you often do not need a separate tool to debug a web implementation. Browser tools show the raw request, payload, response, and timing, but do not decode Adobe-specific parameters, and they show only traffic that originates in the browser. For steps, see Inspect web requests.
HTTP(S) debugging proxies http-debugging-proxies
HTTP debugging proxies intercept HTTP and HTTPS traffic between a client and a server. They are useful when browser developer tools do not provide enough visibility or when the implementation runs outside of a traditional web browser.
HTTPS inspection generally requires configuring the client to trust a certificate supplied by the debugging proxy. Follow your organization’s security policies when installing certificates or intercepting encrypted traffic.
Capture only authorized test traffic and remove sensitive data before sharing captures. Some applications restrict certificate trust or use certificate pinning, so a proxy might not be able to inspect their HTTPS traffic.
Adobe processing diagnostics processing-diagnostics
These Adobe tools show processing that happens after a request leaves the client. For when to use each, see Trace Edge Network processing.