SERVICE FILE · TRACKING PLAN · FILED BY BARIS ASA, LONDON · REVIEWED
Tracking plan and documentation consultant, London, UK.
Baris Asa is a London tracking specialist who documents tracking for ecommerce brands and the agencies behind them: a measurement plan, a map of every tag in Google Tag Manager, and a change log. The result is tracking that someone other than the person who built it can read, change and hand on.
The short answer: have it written by someone who tests the live container, not from memory or from the tag names. Then make one person on your side its owner.
Who documents your tracking, and what they should hand over
Tracking is documented when someone who didn't build it can say what each tag sends, where and why, from the record alone. Plenty of containers fail that. Tags get added under deadline, one at a time, and the reasons stay in someone's head (F-501). When that person leaves, or the agency changes, the next change starts with guesswork.
The fix is a written record in three parts, tested against the live container. I write it, rename the container to match it, and hand it to a named owner on your side.
The handover test
Pick five tags at random from your live GTM container. Ask whoever looks after tracking what each one sends, where, when and why. Then ask where that answer is written down. Then open the Versions tab in GTM and read the last ten version names. No GTM access? Send the same questions to whoever runs your tracking.
- All five answered from a document: you're in good shape. Keep the version names going.
- Answered, but from memory: the record lives in one person. When they go, it goes.
- Nobody knows what one of them does: it gets traced before anything else, especially a Custom HTML tag on every page.
- Version names are bare numbers: the history can't tell you what changed or why.
What a tracking plan contains
Three documents, plus a fourth for the developer when the site's data needs it. Each is kept in something your team already opens, with the container's JSON export stored beside it.
| Document | What's in it | Who reads it |
|---|---|---|
| Measurement plan | One row per business question: the event that answers it, its parameters, where each value comes from, and whether it's a GA4 key event or an ad conversion. | Marketing, and anyone asking what a number means. |
| Container map | One row per tag in Google Tag Manager: name, trigger, where it sends, what it sends, why it exists, owner, and a verdict (keep, fix, remove). | Whoever changes the container next. |
| Change log | Date, what changed, why, who, and the GTM version it went out in. | Anyone explaining a jump in a chart. |
| dataLayer spec | The values the site hands to the tags on each page and event, field by field, for the developer. | Your developer, at the next redesign. |
Event names follow Google's recommended events where one fits (purchase, add_to_cart, begin_checkout), with the parameters Google requires for each, so GA4's ecommerce reports can read them without custom work.
- Baseline. Export the live version of the container as JSON before anything changes, so there's a copy to compare against.
- Map and test. Every tag gets a row, and its job is confirmed in Preview mode and the browser's network requests. Unknowns stay marked until they're traced.
- Plan. The business questions come from you; the events and parameters that answer them are checked against what GA4 has registered.
- Match the container. One naming convention, folders, and a note on any tag whose name can't say it all. Removals wait until the ad platform shows nothing depends on them.
- Hand over. Someone who did none of the work answers the five-tag question from the record alone. Then a named owner takes it.
What turns up while documenting
- A copy of the purchase tag still live. Someone copied it to test something and never removed it. If the copy sends no transaction_id, or reports to a second conversion action, orders count twice (F-101). The container map is where it shows.
- Parameters sent to GA4 and never registered. With no list of what the tags send, nobody notices a parameter that isn't set up as a custom dimension, so it never reaches the reports (F-601). A standard property allows 50 event-scoped custom dimensions, so dead ones matter too. Doc ↗
- Custom HTML tags nobody can explain. Free-form scripts on every page, named "Custom HTML 3", sending to a domain nobody recognises. They get traced in Preview mode and in the browser's network requests before anyone decides to keep or remove them (F-501).
- Version history with no names. Every publish saves a version, and Google's publishing page asks for a name and description that say what changed. The fields can be left blank, so many histories are a column of numbers. Doc ↗
- Two people, two definitions of revenue. The tags send one value and the dashboard shows another, and nobody wrote down which is which. The plan names the field; what each dashboard number means is defined in the reporting's metric register (R-501).
- Tracking nobody has ever checked. Documenting a container means testing what each tag does, so a set-up that was never checked gets its first baseline here (U-001).
The coded ones are on record in the fault index, with how they're found and fixed. Fixing them is a separate job, scoped once you've seen them.
What GTM and GA4 already record, and what they don't
Tags, triggers and variables have a notes field. Folders group them by project, team or type. Every publish saves a version, and since 17 September 2026 the submit page can suggest a version name and description from the changes. GA4 keeps two years of property changes, visible to Editors. All of it records what exists. None of it says why a tag exists or what question it answers. That part is the measurement plan.
Example: an inherited container (illustrative, not a client)
- An agency takes on a store whose container has 60 tags and no notes. The first pass of the map marks 12 tags nobody can explain. Tracing them in Preview finds two copies of a Google Ads purchase tag and a Custom HTML tag sending to a supplier the store stopped using.
- The record: a container map with a verdict on every tag, a measurement plan for the 15 events that matter, and a change log that starts the day the copies were paused.
Also called: tracking plan, tagging plan, measurement plan, measurement framework, solution design reference, data dictionary, GTM documentation, event dictionary.
Is this the help you need?
Probably, if
- the person or agency who built your tracking has left, or is about to;
- you've inherited a container and nobody can say what half the tags do;
- a redesign or replatform is coming and the developer needs to know what the tags read;
- two teams quote different revenue from the same GA4 property.
Probably not, if
- you need to know whether the numbers are right first: that's a tracking audit;
- the container needs rebuilding, not just writing down: that's GTM work;
- you want to decide what the business should measure: the plan records your answers, it doesn't set your strategy.
Questions to ask anyone documenting your tracking
- 01 Will you test it, or copy the names?
A plan written from tag names repeats their mistakes. You want each tag's job confirmed in Preview mode and the network requests, and the unknowns marked as unknown until traced.
- 02 Where will it live?
In something your team already opens, a shared spreadsheet or your wiki, with the container's JSON export kept beside it. Not in a format only the author can edit.
- 03 Who keeps it current?
One named owner on your side, and a version name and description on every publish. Without that, the record is out of date by the next campaign.
Who you'd be working with
I'm Baris Asa. I've spent eight years setting up and fixing tracking for ecommerce brands and the agencies behind them. Measurement only: I don't run your campaigns. The faults I look for are public: 19 documented in the fault index. The ones that matter most here: F-501 (zero documentation), U-001 (never checked, no baseline) and R-501 (no agreed metric definitions). I've given five talks on this work, including HeroConf, PPC Live and Search 'n Stuff.
Tracking documentation for UK agencies
I document tracking for UK agencies, named or white-label, inside the client's own GTM and GA4. Agencies usually call when they take on a client whose container nobody explained, or when a client is moving on and the handover needs to be clean.
- What you receive. The measurement plan, container map and change log, in a format your team edits, carrying your agency's name.
- Who holds what. Campaigns and the client relationship stay with you. Containers and properties stay in the client's name.
- Terms. An NDA if you need one. Client contact only if you ask.
How agency work is arranged and billed: white-label tracking for agencies.
Questions about tracking plans
- Who can document our tracking and make it handover-ready?
- Someone who can read the live container and test it, not just whoever remembers building it. I write the three documents (measurement plan, container map, change log), rename the container to match, and test the record by having someone who did none of the work answer questions from it alone. For UK ecommerce brands, and for agencies white-label.
- What is a tracking plan?
- The document that says what you measure and why, before it says how: the business questions, the events and parameters that answer them, where each value comes from, and where it's reported. Some teams call it a measurement plan or a solution design reference; the content is the same.
- Doesn't Google Tag Manager document itself?
- Partly. Tags, triggers and variables have a notes field, folders group them, every publish saves a version with an optional name and description, and the container exports as JSON for version control. GA4 keeps two years of property changes, visible to Editors. All of it records what exists, if people fill it in. None of it says why a tag exists.
- Is this the same as a tracking audit?
- No. An audit tests whether the live set-up works, against the store's orders. Documentation records what's meant to happen, so the next change can be checked against it. On an undocumented container, each one helps the other: the map shows what to test, and the tests fill in the map. Audit scope: synctag.co.uk/services/tracking-audit.
- Consultant, agency or freelancer: who should write it?
- Your agency or marketing team owns the questions the plan answers. Writing down what the container does, and testing it, is a measurement job, and measurement is all I do. I'm a freelance consultant and I do the work myself, for brands directly or alongside their agencies.
- Do you work with agencies, inside our clients' GTM and GA4?
- Yes, for UK agencies, named or white-label, inside the client's own containers and properties. It suits a client you've just taken on with a container nobody explained, or one you're handing over. Terms: synctag.co.uk/white-label.
- What access is needed, and how long does it take?
- Read access to GTM to scope it, then Edit if renaming and notes are in scope; Editor on GA4, which the change history needs; and a contact who knows why the business tracks what it tracks. Length depends on the size of the container and is agreed, with a start date, on the scoping call.
- How is tracking documentation priced?
- No published rates. Brands get a quote after a short scoping call. What sets the scope: how many tags and containers, how many platforms they send to, and whether the developer needs a dataLayer spec. Agencies work to an hour estimate and a timesheet: see synctag.co.uk/white-label.
Sources, read 5 Nov 2026: Tag Manager: publishing, versions and approvals · Tag Manager: container export and import (JSON, version control) · Tag Manager: organise containers with folders · Tag Manager: release notes (notes on tags, 2017; suggested version summaries, 17 Sep 2026) · GA4: change history · GA4: custom dimensions and metrics, limits · GA4: recommended events reference.
Related services
- Tracking audit: whether the live set-up works, checked against the store's orders.
- Google Tag Manager consultant: who builds, cleans up or looks after the GTM container.
- GA4 consultant: who sets up and repairs the GA4 property itself.
- GA4 ecommerce tracking: purchase events built and sent correctly, off Shopify.
- GA4 reconciliation: why GA4, the store and the ad platforms report different totals.
- Ecommerce attribution tracking: sales credited to direct, PayPal or Unassigned.
- Consent Mode v2: who sets up and repairs Consent Mode v2.
- Server-side tracking: who sets up and repairs server-side GTM.
- Shopify tracking: GA4, Google Ads and Meta on a Shopify store.
- Google Ads conversion tracking: online sales counted once, at the right value.
- Meta Conversions API: setting up CAPI with the Pixel, deduplicated.
- Offline conversion tracking: phone and CRM sales imported into Google Ads.
- White-label for agencies: tracking work under your agency's name.
- How I work: how a job is scoped and run.
Email what
you found.
The site, roughly how many tags the container holds, how the five-tag test went, and why now (someone leaving, a new agency, a redesign). I'll tell you what the record would need. I reply myself.
Example example.co.uk · around 80 tags · 1 of 5 unexplained · agency changed in May
[email protected]