Skip to main content
All CollectionsAudits
Browser Console Logs Report
Browser Console Logs Report
Luiza Gircoveanu avatar
Written by Luiza Gircoveanu
Updated over a week ago


The Browser Console Logs Audit report includes the text of all console messages found in the Audit and when available, maps them to relevant tags. This is powerful for evaluating site health and for potential errors that are impacting data collection and customer experience.

This report helps you quickly see if JavaScript errors are preventing your tags from firing and hurting the integrity of your reports.

Summary Metrics

The top section of the report shows the total number of URLs with a log message broken out by message type, as follows:

Error: This is an important message indicating that a script failed to execute or a resource failed to load. Failing tags are sometimes caused by JavaScript errors, but script errors can also degrade the visitor experience. Use these messages to help troubleshoot what scripts may be causing problems on your pages.

Warning: This is a notice of something that may need action but is not usually urgent.

Information: This is a message in the console. Normally it can be ignored.

Debug: Similar to an informational message, these are messages specific to debugging your site or app.

Other: All other console logs.

This table lists each console message and displays:


  • Some types are more severe and urgent to fix than others. Make sure you understand the different browser log message types so you can act appropriate.

Related tag

  • This insight tells you if the console message is related to one of the technologies on the page. It make this report even more actionable by clearly indicating which tracking technologies are at risk.

The # of instances

  • Use volume of instances in reference to the volume of pages to understand if an issue is happening multiple times per page or with higher frequency.

The # of pages

  • Page volume is a very important factor in evaluating severity of an issue, prioritize the issues that are prevalent across a high number of pages.

You can interact with the summary metrics and the table below in order to filter the results in the Browser Log Messages and the URLs table.

The list of URLs below have unique console message counts to provide a snapshot of the details of that page. Select any URL to open the Page Details report and analyze it further.

Did this answer your question?