Zero documentation

Symptom and cause

Symptom

Nobody can say what fires, when, or why. Every future change, or staff handover, starts as archaeology.

Cause

The container grew by accretion: tags added under deadline, no naming, no record of what each one is for or what depends on it.

Where it's caught

A container full of unnamed tags and triggers; no measurement plan; the previous setup's logic living only in someone's head.

Why containers end up undocumented, and what GTM records on its own

No container starts undocumented. It gets there one deadline at a time. A launch needs a pixel by Friday, so someone pastes in a Custom HTML tag (a free-form script) and calls it "Custom HTML 3". A contractor adds three Google Ads tags for a campaign and moves on. A developer copies the purchase tag to test something and never deletes the copy. Each change made sense on the day. None was written down.

The cost shows up later. A copied purchase tag can count orders twice (F-101), for example when the copy sends no transaction_id or reports to a second conversion action. A new hire pauses a tag that fed a bidding strategy. A redesign removes a dataLayer push (the data the site hands to the tags) and nobody knows which tags read it. A parameter nobody listed is never registered in GA4 (F-601). When GA4 and the store disagree, nobody can say whether a tag or a report is wrong.

Tag Manager and GA4 keep part of a record on their own. All of it is optional, and none of it holds the reason:

Notes. Each tag, trigger and variable has a notes field, opened from the more actions menu with Show Notes. Blank unless someone writes in it.

Folders. Group tags, triggers and variables by project, team or type. They show where a tag belongs, not what it is for.

Versions. Every publish saves a version. Google's guidance is to give it a name and description that make the change easy to understand. Tag Manager will publish without them, so many histories are a list of numbers. Since 17 September 2026 the submit page can suggest a name and description from the changes. It summarises what changed; the reason is still yours to add.

Export. The container downloads as JSON, which can be kept in version control and compared. Every setting, no intent.

GA4 change history. Two years of property changes, visible to Editors. Each row shows when, the item, the action and who made it; the row's information icon shows the before and after.

The piece no tool writes for you is the measurement plan: the business questions, the events and parameters that answer them, and where each is reported. Without it, the container is its own only description.

The threshold is the handover test. If someone other than the builder cannot say what each tag sends, where and why, from the record alone, it is F-501. Whether the tags work is a separate question.

Tag (as named)	Sends to	Why it exists	Verdict
GA4 · Event · purchase	GA4	revenue reporting	keep
Meta Pixel	Meta	not recorded, owner left	fix: name, note
Custom HTML 3	unrecognised domain	nobody knows	trace first
Copy of Google Ads conversion	Google Ads	unknown; may double count (F-101)	remove after checks
Measurement plan	n/a	none on file	write first

runs on every page, nobody can say why

How to catch it

1. You can check the first three yourself. Run the handover test: pick five tags at random from the live container and ask whoever looks after tracking what each one sends, where, when and why. Then ask where that answer is written down. An answer that lives only in someone's head is the finding.
2. Ask for the measurement plan. If one exists, compare its last edit date with the date in the Published column on GTM's Versions page. A plan last edited a year before the latest publish describes a container that no longer exists.
3. Open Versions and read the last ten names and descriptions. Bare version numbers with no description mean the history cannot tell you what changed or why.
4. The next three need someone with GTM and GA4 Admin access. Scan the Tags list for names that say nothing: "Custom HTML 3", "Copy of", "test", "new", a person's or supplier's name. Notes do not show in the list, so open each one. Start with Custom HTML tags on the All Pages trigger: they run on every page and can send data anywhere.
5. Compare GTM with GA4. List the event parameters your GA4 tags send, then open Admin → Data display → Custom definitions. Parameters sent but not registered are F-601. Registered dimensions that nothing sends any more still count towards the limit of 50 event-scoped dimensions on a standard property.
6. Read GA4's property change history for the last year (Editor role needed). Note who changed key events, filters and links, and whether they are still around. A change nobody can explain is an undocumented change.

What putting it right involves

1. Take a baseline before touching anything. In Admin → Export Container, choose the most recent version with a date in the Published column of the Versions page (the live one), not a workspace, which can hold unpublished changes. Store the JSON where it cannot be lost, ideally in version control.
2. Build the container map. One row per tag. Columns: tag name, type, trigger, destination, what it sends, why it exists, owner, verdict (keep, fix, remove). Work out the unknowns in Preview mode (GTM's test view of which tags fire) and in the browser's network requests, not from guesses.
3. Write the measurement plan. One row per business question. Columns: question, event, parameters, dataLayer source, tags that send it, registered in GA4 (yes or no), key event or Google Ads conversion. Keep the reporting definitions beside it: which revenue field means what is the metric register (R-501).
4. Make the container match the plan. Rename to one convention, for example "GA4 · Event · purchase" or "Meta · Pixel · PageView". Group with folders. Put a note on every tag whose name cannot say it all, every Custom HTML tag above all.
5. Retire with care. Before pausing a tag marked remove, find out in Preview mode which conversion action or pixel it hits, and check that action's status and recent conversions in the ad platform. Pause, publish, then watch that action's count and any bidding strategy that uses it for a few weeks before deleting. Record why in the version description.
6. Keep the record current. Every publish gets a version name and description saying what changed and why. If you use the AI-suggested summary, add the why yourself. One person owns the plan.
7. Test the record. Someone who did not do the work answers the five-tag question from it alone. Rerun the test whenever the tracking owner changes.