Ledger

Run a Ledger Audit

Run an audit from a Ledger project to scan one GTM workspace. Each run produces the Marketing, Business Analyst, Technical and Media reports, linked from the project page.

Before you start

You need a project with a valid GTM Container URL. See Set Up a Ledger Project.

Run an audit

  1. Open Ledger > Projects and click the project.
  2. Click Run New Audit (or Run Audit on a project with no audits yet).
  3. Enter the Workspace Name to scan, for example Development or QA. Leave it blank to scan Default Workspace. The name is matched against the container's workspaces, ignoring case.
  4. If the property has enabled AutoTag projects, choose them under AutoTag Projects (Media Report). All are ticked by default; the ones you keep are grouped in the Media report.
  5. Click Run Audit.

A new row appears under Recent Audits with the status Queued. The page checks for updates every 10 seconds while an audit is queued or generating.

Open the reports

When the status reaches Completed, the View column shows one icon per report:

IconReport
View Marketing ReportPlatforms, events and consent at a glance
View Business Analyst ReportConsent statistics and action items
View Technical ReportFull trigger lists and variable dependencies
View Media ReportCoverage grouped by the AutoTag projects you picked

Each opens a standalone page in a new tab with its own shareable URL. If the Media icon does not appear right after completion, reload the page.

The table lists the 20 most recent audits, with the Workspace, Created and Completed times. The report contents are described in Generate a Report.

Delete an audit

Click the trash icon in Actions and confirm.

Troubleshooting

ProblemCause and fix
Failed with "Workspace '...' not found"No workspace has that name. Check the name in GTM and run again
Status stays QueuedThe GTM Container URL may be missing the account or container number. Edit the project, paste the full workspace URL, and run again
Failed with another messageThe message is shown in the View column. Check that TagPipes still has read access to the container