Skip to content

How to audit the analytics and marketing tags on a web page

Updated October 11, 2026

Tags are easy to add and hard to keep track of. A page can end up with two copies of the same container, a retired Universal Analytics snippet, an ad pixel that ignores the consent banner, or an email address inside a request. This guide shows how to check a page, and what to look for.

What a tag audit looks at

  • Which tags are present, and with which account, container or pixel IDs.
  • Whether each one loads once, and sends the events you expect.
  • What the data layer contains and in what order.
  • How consent is applied: what runs before a choice, and after accepting or rejecting.
  • Whether any request carries personal data it should not.

Option 1: browser DevTools

Open DevTools, choose the Network tab, reload and filter by a vendor's host (for example google-analytics.com or facebook.com/tr). You can see every request in full, including bodies and headers. It is exact, but you need to know the hosts and parameter names, and nothing summarises the result.

Option 2: AnyTool Tag & Pixel Inspector

The extension scans the page you are on and presents the same facts as a report: recognised tags and IDs, the hits they sent, the data layer, consent state and cookie names, followed by findings that explain what looks wrong and how to fix it.

  1. Open the page and click the AnyTool Tag & Pixel Inspector icon, then choose Scan This Page.
  2. Read Findings first. Each one names the problem, explains why it matters and says how to fix it.
  3. Open Tags to confirm the IDs match the accounts you expect, and Requests to see the events each tag sent.
  4. Open Data layer to check event names and parameters in the order they were pushed.
  5. Turn on Live, then perform the action you are testing (accept the banner, add to cart, submit a form) and watch the new requests and events arrive.

Checking consent properly

Scan the page before choosing in the consent banner, then reject and scan again, then accept and scan again. Compare which tags and requests appear. Google tags can respect Consent Mode, but other advertising pixels usually need to be blocked until consent, which the report flags when it sees them sending while ad_storage is denied.

Limits worth knowing

  • Browsers show an extension a request's address and timing, not its body, so hits sent as POST bodies appear without their parameters.
  • Server-side tagging on your own domain and blocked requests are not visible.
  • The inspector recognises a curated list of well-known vendors; other scripts are not listed.
  • Findings are prompts to investigate, not legal advice about what your visitors must consent to.

Keeping UTM links tidy

Campaign tagging problems often start in the link rather than the page. The AnyTool Studio UTM Analyzer and Campaign URL Builder help keep parameters consistent before they reach your analytics.