This will save you a lot of headaches.

[kexej28769@nongnue]

I guarantee you will forget. So you want to put that variable there so you change it once and it's everywhere. You're saving yourself so much time and hassle. Just use a Google Analytics ID variable. If you have a really old container, the variable probably wasn't there when you first set it up. So one of the things I would recommend is to check and make sure you're using the variable. If you're not, create a task for yourself to remove all hardcoded instances of your GA ID and replace it with the variable instead.



2. Create a default container to import into
So the next thing — agencies, this is for you — create a benin number data container to import from. Obviously, if you’re working in-house, you’re probably not going to be building Google Tag Manager containers very often, unless you’re working as a home builder and you’re building microsites for every new home development. Then you’ll want to create a default container for yourself. But definitely on the agency side, you want a default container that you build every cool container that you think of, oh, we need to track that, just put it all in your default container, and then when you’re grabbing it to build for a client, you can decide, oh, we don’t need that, or yeah, we need that.

This is going to save you a ton of time when you're setting up containers, because I find that the most laborious part of working with a new Tag Manager container is thinking, "What things do I want to include?" So you want to make sure that your default container has all of your little tips and tricks that you've collected over the years in there and of course documented, and then decide on a client-by-client basis what you're going to leave out and what you're going to keep.