At Penn Libraries, we've been working on adopting Google Tag Manager. We already use on many of our sites, with great results thus far.
We have a long list of GA web properties, and I've personally found it helpful to give each property its own GTM container. Some of our containers have complicated, site-specific tags/conditions/variables that don't really belong in other sites; I find it easier to maintain them separately. On the other hand, I'm sure there are plenty of advocates out there for using a single container.
My impression of GTM is that you can use containers in whatever way best suits your needs. Need one container for all your properties? That's fine. Need a different container for every property? That's also fine.
-- Ivan Goldsmith
Penn Libraries Web Unit
From: Code for Libraries <[log in to unmask]> on behalf of Eades, Lynn <[log in to unmask]>
Sent: Tuesday, June 28, 2016 7:56 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Implementing Google Tag Manager
The University Libraries here at UNC-Chapel Hill are currently working with a consultant to set up Google Tag Manager. We also had several GA accounts for our many websites. Within GTM, we have one container/account for all the sites. This way we can see the flow of traffic between our sites. The consulting firm, SearchDiscovery out of Atlanta, have been wonderful to work with and have really helped us in setting this up.
We are just about to wrap up our work with the consultant. Would be happy to discuss further if desired.
B. Lynn Eades
Web Development Librarian
Health Sciences Library
335 South Columbia Street
University of North Carolina at Chapel Hill
Chapel Hill, NC 27599-7585
Phone: (919) 966-8012
Email: [log in to unmask]
Connecting people everywhere with knowledge to improve health
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Kyle Breneman
Sent: Tuesday, June 28, 2016 7:28 AM
To: [log in to unmask]
Subject: [CODE4LIB] Implementing Google Tag Manager
Has anyone out there implemented Google Tag Manager? I'd like to get it up and running for all of our library's web properties this summer, but I'm a bit uncertain how I should be structuring it. The most immediate question is, "Do I need only 1 container, or do I need more than 1 container?"
Right now, we are tracking our main website, our library blog, LibGuides, ArchivesSpace, EDS, and several other things. Most of these are set up as separate "properties" of one umbrella GA account for the library. This existing structure leads me to believe that I want to configure Google Tag Manager with multiple containers: one container for the main library website, one container for our blog, one container for ArchivesSpace, etc.
Does that sound correct? Is there anything else I should be mindful of as I setup GTM?