PlugsightDocs

Tag Manager container audit

Audit your Google Tag Manager container for tags that never fire, retired Universal Analytics tags, duplicates, unused triggers and unpublished changes.

Find tracking problems in your live Tag Manager container, ranked by how much they matter.

What you'll get

  • Problems found in the published (live) version:
    • tags with no firing trigger, which never run (high)
    • Universal Analytics tags, which collect nothing since Google retired UA (high)
    • paused tags (medium)
    • possible duplicates: tags of the same type with the same id, which can double-count (medium)
    • triggers no tag uses, and variables nothing refers to (low)
    • Custom HTML tags, to check they're still needed
  • Changes waiting unpublished in workspaces.
  • A fix-first list in plain words.

What you need

Ask this

Using Plugsight, audit my Google Tag Manager container. List the problems by severity, explain each in plain words, and tell me what to fix first. Are there unpublished changes waiting in any workspace?

Variations

  • Several containers: "Audit GTM-ABC123." When the MCP server reaches more than one container, name it.
  • One tag: "Which GA4 measurement id does the GA4 config tag send to, and on which triggers?"
  • Double counting: "Are any of our conversion tags firing twice?"
  • History: "How many tags, triggers and variables did each of the last five published versions have?"

What your AI does behind the scenes

  1. Lists the containers the MCP server reaches (tag_manager_list_containers).
  2. Audits the live version of the container (tag_manager_audit).
  3. For detail, reads the container's tags, triggers and variables (tag_manager_container), or one tag in full (tag_manager_get_tag).
  4. For history, lists the published versions (tag_manager_versions).

Does it change anything?

No. Tag Manager is read-only in Plugsight: your AI can't edit, publish or delete anything. Make the fixes in Tag Manager.