Packet analyzers

Packet analyzers let you view the data sent by your implementation to Adobe data collection servers.

Similar to the Adobe Experience Cloud debugger, a packet monitor shows what data parameters are being passed in an image request; however, packet monitors provide added functionality:

  • View custom link tracking image requests
  • View image requests using implementation methods other than JavaScript, such as hard-coded image requests or Appmeasurement

To view Analytics requests, filter outgoing requests using “b/ss”.

In very rare cases, the debugger will report an image request although no request makes it to Adobe’s Analytics processing servers. Using a packet monitor is a great way to be 100% sure that a specific image request is being fired successfully.

While Adobe does not provide an official packet monitor, there are a wide range of them on the internet. The following are some packet monitors others have found useful.

These lists are not meant to be comprehensive, but rather information on frequently used monitors.
Internet Explorer
Standalone Programs
Observe Point (tag viewer)
Observe Point (tag viewer)
Chrome Developer Tools
Tamper Data
Firebug Lite
Adobe does NOT support or troubleshoot any issues you experience with these packet monitors. Consult the packet monitor’s originating site for assistance.

Typical HTTP response status codes

When AppMeasurement sends data to Adobe data collection servers, servers respond with a response status code.

  • 200 OK: The most common response from data collection servers. The image request was successfully received and a transparent image was returned.

  • 302 FOUND: There are a couple possible reasons to receive this response:

    • The first image request of a visitor: A redirect occurs if a user visits your site for the first time. This redirect is to obtain a visitor cookie. It does not affect data collection.
    • Integration between Comscore and Adobe: If your organization uses a Comscore/Analytics integration, each image request always results in a 302 response.
  • 404 NOT FOUND: This response means that the image request was not found, and data is not sent to Adobe data collection servers. This response is also possible when hardcoded image requests are not formatted correctly. Work with the individual or team who implemented Analytics to resolve this issue.

NS_BINDING_ABORTED in response codes

This message occurs because the link tracking image request is designed to let the browser proceed to the next page before waiting for a response from the Adobe data collection servers.

Adobe’s response to the image request is simply a blank 1x1 transparent image, which is not relevant to the content of the page. If you see a line item in your packet monitor from Adobe, either with a 200 OK response or an NS_BINDING_ABORTED response, the data has reached Adobe’s servers. There is no need to have the page wait any longer.

Packet monitors integrated as a plug-in rarely see the full response. They tend to see the request as aborted because the full response was not received. These monitors also rarely make a distinction between whether it was the request or response that was aborted. A stand alone packet monitor typically has more detailed messages and reports the status more accurately. For example, a user may get a message in Charles saying “Client closed connection before receiving entire response.” This means the data did reach our servers, just the browser moved on to the next page before the 1x1 pixel was received.

If an external packet monitor reports that the data collection request is aborted, rather than the response, this is a cause for concern. Adobe Customer Care can provide help in troubleshooting.