The headers common to all Audit exports are described here. The first 17 columns are common to each export, while the remaining columns are tag specific.

The URL is listed as many times as the tag fired on that page.

This is the number of JavaScript errors detected on a page.

This is the code returned from the server. It indicates if the tag was accepted (200-level), redirected (300-level), sent insecurely (0--for Google only) or other statuses as defined by the W3C.

This is the size of the page in bytes with all its assets.

This is the amount of time, in milliseconds, that the page took to load.

The parent URL is where the current URL was found. In effect, this becomes the referrer, though the page is not actually accessed by clicking on the link.

This is the data repository that the tag directed the data to. In the case of Adobe Analytics, this represents the report suite.

This is the version of the tag, if any is captured. Not all tags have the versions exposed.

The tag position represents how far down the document.links object the URL of the tag appears. This is expressed in percentage and roughly corresponds to where on the page the tag fires. A value of 0.1 means the tag is located near the top, while 0.9 means the tag is found near the end of the document. Executing near the top or bottom of the page load can affect the tag's accuracy; if a page renders slowly in the browser, a tag located near the bottom might not actually load if the user clicks to another page before that tag is fired.

A multiple tag is logged when more than one instance of the tag fires on the page. A multiple is different from a duplicate tag because the tags will not be identical. Multiple tags are generally useful for detecting click tracking, exit links, downloads or other interactions on a page.

A duplicate tag is an exact copy of another instance of the tag which fires when the page loads. Duplicates for web analytics tags inflate metric counts and should be eliminated. Duplicates for other types of tags (non-web analytics) might be acceptable, such as a tag manager bootstrap or social tag loading more than once.

If the tag passed the Vendor Rules on the page it is shown as TRUE, or if the tag failed it is displayed as False.

This is the size of the tag in bytes.

This is the time, in milliseconds, after the page begins to load when the tag begins to load.

This is the time, in milliseconds, after the page begins to load when the tag has completed loading.

This is the total time, in milliseconds, that it took the tag to load. It is calculated by subtracting Tag Started At from Tag Stopped At.

This is the time, in milliseconds, that the tag finished loading. It is the same as the Tag Stopped At.