GTM Base Container

February 12, 2026
  • First Published: February 12, 2026
  • Last Modified: February 17, 2026

Setting up tracking for a new client should be a moment of momentum, not a tedious slog through repetitive tasks.

If you’re a freelancer or working within a digital agency, you know the drill: you open a fresh Google Tag Manager (GTM) container and start manually building the same GA4 configuration tags, the same scroll trackers, and the same Google Ads conversion linkers you’ve built a hundred times before.

It’s time-consuming, it’s prone to human error, and frankly, it’s a bit of a bore.

To paraphrase Yoda, there is another (way).

By using a GTM Base Container, you can transform a multi-hour setup into a two-minute import. This isn’t just about saving time; it’s about codifying your expertise so that every client gets your “gold standard” tracking from day one.

Table of Contents

Key Takeaways

    • Efficiency is King: Import a pre-built container in seconds rather than building tags from scratch.

    • Standardisation: Maintain consistent naming conventions across all client accounts.

    • Customisation via Variables: Use Constant Variables to update IDs (like GA4 Measurement IDs) in one single place.

    • Platform Specifics: Create “Master” containers for different platforms like Shopify, WooCommerce, or specific booking engines.

What Exactly is a Base Container?

Think of a base container as your ultimate “starter kit.”

It is a GTM container that you’ve pre-populated with all the tags, triggers, and variables that you consider essential for any project.

Instead of starting with a blank canvas, you start with a fully-realised framework.

For instance, you might have one standard base container for lead-generation sites and others specifically tailored for ecommerce platforms like Shopify or WooCommerce.

A Google Tag Manager Base Container is a great way for you to ensure you have a unified and codified approach to managing new containers for your multiple clients.

Base Containers in GTM

The Secret Sauce: Constant Variables

The biggest hurdle people imagine when “copying” containers is the different IDs.

Your new client obviously doesn’t share the same GA4 Measurement ID or Google Ads Conversion ID as your last one.

This is where Constant Variables save the day.

When you build your base container, don’t hard-code your IDs directly into the tags.

Instead, create a Constant Variable for your GA4 ID, your Facebook Pixel ID, and your Google Ads ID.

Link your tags to these variables.

When you import your base container into a new client’s GTM account, you only have to change the value in that one variable.

Every tag using that variable updates instantly. It’s elegant, fast, and significantly reduces the risk of typos.

How to Deploy Your Base Container

The process is remarkably simple, but there is one “gotcha” to watch out for.

Here is the workflow:

  1. Export: In your Master GTM container, go to Admin > Export Container. This gives you a JSON file.
  2. Import: In your client’s GTM container, go to Admin > Import Container.
  3. Choose Your Workspace: Select the workspace you want to import into (usually ‘Default’).
  4. The “Merge” Rule: This is crucial. If the client already has tags in their container, always choose ‘Merge’, not ‘Overwrite’. Overwriting will wipe out everything they’ve already built. Within the merge option, you can choose to rename conflicting tags or overwrite them if yours are the updated versions.
  5. Update Variables: Head to your Variables tab, swap out the placeholder IDs for the client’s actual IDs, and you’re ready to test.

What Should Be in Your Base Container?

Every agency has its own “secret sauce,” but a solid base container usually includes:

  • Google Analytics 4: The configuration tag and standard events (like a custom scroll tracker if you prefer more control than the built-in GA4 version) and standard event settings.
  • Google Ads: The Conversion Linker and a standard Purchase event.
  • Paid Social: Configuration tags for Meta (Facebook) or LinkedIn.

Naming Conventions

This is often overlooked.

By using a base container, you ensure every tag is named exactly the same way (e.g., GA4 – Event – Lead Form) across every client.

This makes it much easier for your team to jump between accounts.

Base Container Tags

Better for You, Better for the Client

At the end of the day, using a base container makes you look like a pro. You can show your clients a fully-functional tracking setup within minutes of getting access. It allows you to spend less time on the “plumbing” and more time on the high-value work: analysing the data and finding growth opportunities.

So, are you going to keep building from scratch, or is it time to codify your process?

Frequently Asked Questions

Can I use this if the client already has GTM set up?

Absolutely. Just ensure you select the Merge option during the import process. This allows you to add your standard tags alongside their existing ones without breaking anything.

What if I work with different niches?

It’s best to have a library of base containers. You might have one for “Standard Lead Gen,” one for “Shopify Ecommerce,” and perhaps one for “Specialised Booking Engines.”

Do I still need to test everything?

Yes. Every website is built differently. While the tags and triggers are ready to go, you must still use GTM Preview mode to ensure the website’s CSS selectors or data layer events match what your triggers are looking for.

Kyle

Author

Hello, I'm Kyle Rushton McGregor!

I’m an experienced GA4 Specialist with a demonstrated history of working with Google Tag Manager and Looker Studio. I’m an international speaker who has trained 1000s of people on all things analytics.

Find out more About me
Scroll to Top