gtm-tag-auditlisted

Audits tag management containers (Google Tag Manager, Matomo Tag Manager, Tag Commander/Commanders Act) into a structured Excel workbook, from client-side code found on a site (gtm.js, container_XXX.js, tc_*.js, i.e. pre-audit without container access) or from an interface/API export (full audit). Lists each tag with vendor, exact event and data sent, trigger, blocker, Tag Commander scope (périmètre), status and consent mechanism; several tools on one site go in one workbook. Use whenever the user shares or mentions a tag manager container, export or container code (`var data = {"resource"`, `MatomoTagManager.addContainer`, `tagContainer Generator`, `tC.launchTag`, a GTM-XXXXXXX ID), or asks for a tracking audit, pre-audit, full audit, "what does this site send to Meta/GA", "list the tags with their triggers", or in French "audit de tracking", "pré-audit", "audit complet", "liste-moi les tags avec leurs déclencheurs", even without naming the tool.
SW-Vincent/Homebrew-Claude-skills · ★ 0 · Data & Documents · score 72

Install: claude install-skill SW-Vincent/Homebrew-Claude-skills

# Tag management container audit (GTM, Matomo Tag Manager, Tag Commander) ## What this skill does A tag container is unreadable as is: numeric indexes, trigger logic scattered across structures, third-party templates whose name says nothing about the vendor. This skill turns it into a usable audit: an Excel workbook that says, for each tag, **where the data goes, which data exactly, under which conditions (trigger, blocker, scope) and under which consent**, plus a reading of the sensitive points that an account manager or a DPO can read without opening the tool. It is a static reading: conclusions are ideally checked in the Preview/Debug mode of each tool on the live site. Say so in the answer. Write the workbook and the chat answer **in the user's language** (`lang` in the spec, `en` or `fr`). This skill is written in English, the deliverable is not. ## Step 0. Frame the audit: mode and platforms Two modes, which can coexist from one platform to another on the same site: | Mode | Situation | Source | What the source does not show | |---|---|---|---| | **Pre-audit** | no access to the client's or prospect's container | client code: the file loaded by the page | tag names (GTM, MTM), trigger names (GTM, MTM), infrastructure tags, drafts, Tag Commander consent | | **Full audit** | access to the container | interface or API export | nothing major (except Tag Commander: export format not documented) | Recognise the platform and the kind of source from these signatures: |