Open Tracked/Guides/Delete Google tag manager container

Delete Google tag manager container

Deleting a container is easy and hard to undo. Back it up, remove it from the site first, then delete.

5 min read · Updated October 26, 2026

In this guide

Before you delete Step by step If it is a server container What if I delete by mistake?Common problems A cautious alternative to deleting Frequently asked questions

Key takeaways

Export the container first. Then remove the snippet from the website, then delete.
For a server container, also remove the tagging domain and cancel or change the hosting, so you stop paying and stop receiving requests.
Tag Manager keeps a deleted container in a trash for a limited time, so you may be able to restore it. Do not rely on it.

You may want to delete a container because a site closed, because you merged two containers into one, or because you are moving to a new setup. It takes one click, and a wrong click can break tracking on a live site. This page lists the steps that keep it safe. It also covers the part people forget: the server container and the hosting behind it. See Google Tag Manager audit if you are deciding what to keep.

Before you delete

0 of 5 done

I exported the container as a JSON file and saved itI know which websites use this container IDI checked that no other tool depends on it (such as an A/B tool that calls it)I told the team and the clientI wrote down the IDs of the accounts it sent data to

Set up in minutes

Connected in minutes

Add your domain, install the pixel, connect your ad platforms and watch the first events land.

Step by step

Export the container

In Admin, Export container, choose all, and save the file.

Remove the snippet from every site

Search the website code and the theme for the container ID. Remove both parts of the snippet.

Wait and check

Check that the container no longer receives traffic: in Preview or in the version reports.

Delete the container

In Admin, container settings, Delete.

Remove related items

Old users, linked accounts, and tags in other containers that sent to it.

If it is a server container

A server container has extra pieces. The tagging subdomain still points to a server. The hosting may still be running and billing. The web container may still send events to it. Remove these in this order: change the web container so it no longer sends to the server container, wait until no requests arrive, remove the tagging domain, delete the server container, then cancel or downgrade the hosting. With Open Tracked, remove the domain in Settings, Domains, and change the plan if you no longer need it. If your tagging subdomain still has a DNS record, delete that too, so nobody can take it over later.

Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

What if I delete by mistake?

Tag Manager keeps deleted containers in a trash for a limited time, and a container can usually be restored from there. After that it is gone. This is why you export first: an exported file can be imported into a new container at any time. The restored or imported container has a new ID, so you will need to update the snippet on the site.

Common problems

SymptomTracking stops on a live site

Likely causeThe snippet was left in the page and now points to a deleted container.

FixRemove the snippet, or restore the container.

SymptomServer requests keep arriving

Likely causeThe web container still sends to the server container.

FixUpdate the web container first.

SymptomBilling continues

Likely causeThe hosting plan is still active.

FixCancel or downgrade the plan.

SymptomA DNS record is left over

Likely causeThe tagging domain still points to the host.

FixDelete the record.

A cautious alternative to deleting

If you are not sure whether anything still depends on a container, do not delete it first. Remove the snippet from the site and leave the container in place for a month. Watch your reports, and ask the team and the client whether anything stopped working. If a month passes and nothing breaks, export it one more time and delete. A month of waiting costs nothing, and it protects you from the rare case where an old landing page, a partner site or a mobile app still calls the container. Those are the failures that are hardest to explain afterwards.

For agencies, add the container to a short log of retired items: the ID, the site, the date, who approved the deletion and where the export is stored. When a client asks six months later what happened to the old setup, you can answer in a minute.

Works worldwide

Runs on your domain, anywhere

Your tracking runs on your own domain, so a visit from any country is handled the same way.

Frequently asked questions

Can I recover a deleted Google Tag Manager container?

Usually, for a limited time, from the trash. After that, only from an export you saved.

Do I need to remove the snippet before deleting?

Yes. Leaving it points the site at a container that no longer exists.

What happens to the hosting of a server container?

It keeps running and billing until you cancel or downgrade it.

Should I delete the tagging domain DNS record?

Yes, so nobody else can claim it.

Is there a better option than deleting?

You can pause tags or remove the snippet and keep the container for a while.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Guides →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?