Overview
Ledger is the read-only answer to "what's actually in our GTM container right now?" It connects to a container, scans every object, and produces four interactive HTML reports in one run, each pitched at a different stakeholder. Marketers get a report that speaks their language. Business analysts get the same data structured around consent stats and action items. Engineers get the full technical picture with trigger lists and variable dependencies. And the Media report groups the AutoTag projects you select so you can see container coverage organized by managed project.
Unlike Auditor, Ledger never modifies your container. It reads, it analyzes, it reports, and it leaves everything where it found it. That makes it the right tool for one-off audits, client deliverables, and pre-engagement discovery where you don't have write access or you don't want to take any action yet.
Create a project
Open Ledger > Projects and click Add Project. Enter your GTM container URL or container ID. Ledger needs read access to the container; if you're auditing a client's container, they'll need to grant you read access in GTM before you can scan.
Name the project after the site and engagement so you can find it later. "Acme GTM Audit Q2 2026" beats "Test 3". Each project can generate multiple reports over time, which is useful for measuring progress on remediation.
The four reports
Every Ledger run generates four reports together, not one you choose between. Marketing is a simplified view with tag cards, focused on what matters to digital marketers: which platforms are tracked, what events fire, whether consent is wired. Business Analyst is the detailed view, with consent statistics, action items, and breakdowns intended for someone responsible for project-managing remediation. Technical is the full engineering audit, including complete trigger lists, variable dependencies, and container-level metadata. Media groups the AutoTag projects you select so coverage is organized by managed project.
All four read from the same container scan; the difference is the presentation layer. Because they're produced in one pass, you can hand each stakeholder the view that fits them without rerunning anything. For the Media report, select the AutoTag projects to group in the multi-select before generating; all enabled projects are selected by default.
Generate the report
Click Generate Report. Ledger connects to the GTM container, enumerates every tag, trigger, variable, and folder, and produces the Marketing, Business Analyst, Technical, and Media reports as interactive HTML documents. The scan typically finishes in under a minute for small containers; larger ones (500+ tags) may take several minutes.
The generated report is a fully standalone HTML document. All the styling and interactivity is bundled in, so the URL works in any browser without dependency on the TagPipes app. This matters when the report gets emailed around or embedded in a client portal.
View and share
Generated reports are hosted on CDN with a public URL. Share the URL with marketing teams, legal, agencies, or whoever needs to see the state of the container. The report shows which tags are managed by TagPipes (generated via AutoTag) versus which tags are unmanaged (added directly in GTM by humans). That distinction matters because unmanaged tags are the ones most likely to drift and cause problems.
If the report needs to stay private, password-protect the project before sharing the URL. Reports are snapshots, so once generated they don't change; regenerate when the container changes and share the new URL when remediation is done.
Ledger is strictly read-only and never modifies your GTM container, so there's zero risk of disrupting live tracking while you investigate. Reports flag paused tags, potential conflicts, and legacy bloat that's been sitting in the container unnoticed. Each run produces all four reports together, so the Marketing report is best for stakeholders who need a quick overview, the Technical report includes the full trigger lists and variable dependencies that engineers actually need (multi-trigger tags are displayed as a complete list rather than truncated to a single trigger), and the Media report organizes coverage by the AutoTag projects you selected.
Troubleshooting
Ledger can't connect to the GTM container
Verify read access is granted on the GTM account for the user or service account TagPipes uses. The GTM API returns a generic permission error for both missing access and wrong container IDs, so double-check the container ID matches the one in GTM's admin panel. If access is correct and the ID is right, check whether the container is in a restricted workspace.
Report generation takes a very long time
Container size drives scan duration. A container with 1,000+ objects may take several minutes to scan because GTM's API rate-limits per request. Let it complete; if it still hasn't finished after 10 minutes, open support with the container ID so we can investigate stalled scans.
Tag shows as unmanaged when it was generated by AutoTag
AutoTag-managed tags carry specific notes that Ledger uses to identify them. If someone edited the tag notes in GTM, the management signal is lost. Regenerate the container through AutoTag to restore the managed-tag markers, then rerun Ledger to see the corrected count.