Analytics and Tracking

Publish

Also called Go live, container publish

The step that makes a saved container version live, replacing whatever tracking code your visitors were being served before.

Quick facts: Publish

Category
Analytics and Tracking
Also called
Go live, container publish
Level
Beginner
Affects
Live tracking, data continuity, incident recovery
Where to see it
Google Tag Manager (Submit, Versions tab), Tag Assistant
In this article4
  1. How publishing works
  2. Why publishing matters
  3. Common mistakes with publishing
  4. How to publish safely

How publishing works

Every website with Tag Manager installed loads one container file. Publishing swaps that file for the version you have chosen. From that moment every new page view runs the tags, triggers and variables in the published version, and the previous set stops running entirely. There is no gradual rollout and no partial state.

In the interface, Submit saves your edits as a version and publishes them in a single action, which is why the two steps are so easily confused. You can also publish an older version straight from the version list, which is how a rollback is performed. Either way the change reaches visitors within moments, because the container is fetched from Google rather than from your own hosting.

Why publishing matters

It is the point at which a tracking change becomes real, and therefore the point at which data either continues or stops. A conversion tag that is saved but never published records nothing, and the campaign it belongs to looks weaker than it is. The reverse is just as common: a half-finished tag published by accident starts counting the same action twice, and the ad platform then optimises towards a number that was never true.

Publishing is also the only event in a container that carries a timestamp and a named person. When reported figures shift without explanation, the first question worth asking is what was published, by whom and when. Investigating anything else first usually costs a day.

Common mistakes with publishing

Publishing straight from the editing screen without testing is the classic error. Preview exists precisely so a change can be watched firing on a real page before anyone else sees it, and skipping it turns the live site into the test environment.

The second mistake is publishing while a colleague’s unfinished work sits in the container. A publish takes the whole container rather than only your edits, so their half-built tag goes live alongside yours. Read the list of changes the interface shows you before confirming.

How to publish safely

Test in preview mode first, read the summary of what will change, then publish with a version name a stranger could still understand a year later. On a commercial site, avoid publishing just before a weekend or a campaign launch, when nobody will be watching the reports closely enough to catch a problem.

Afterwards, check the live site rather than the interface: load a page, complete the action you are tracking, and confirm the event arrives in the destination platform. If it does not, republish the last known-good version while you investigate, rather than attempting repairs on a live container.

Do and do not

Do

  • Test in preview mode before every publish
  • Read the change summary before confirming
  • Verify the live site straight after publishing

Do not

  • Publish a container holding unfinished work
  • Publish just before a weekend or launch
  • Repair a broken tag live instead of rolling back

Questions people ask about this

How long does a published change take to appear?

It reaches visitors almost immediately, because browsers fetch the container from Google rather than from your own hosting. What does lag is the reporting. Platforms such as GA4 and Google Ads process incoming events on their own schedule, so an empty dashboard shortly after publishing is not evidence that the tag has failed.

Can I undo a publish?

Yes, by publishing again. Open the version history, choose the last snapshot you know was working, and publish that one. The site returns to its earlier behaviour within moments. What cannot be recovered is the data missed while the broken version was live, which is exactly why testing belongs before the publish rather than after it.

Who should be allowed to publish?

Keep the publish permission with the smallest group that can genuinely be held responsible, and give everyone else edit access instead. Editors can build and save work; only publishers can make it live. Where an agency, a developer and an in-house marketer share one container, that split prevents accidental releases far better than a written rule.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.