Hi Kyle,

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.

Lynn
__________________________________________________
B. Lynn Eades
Web Development Librarian
Health Sciences Library
335 South Columbia Street
CB# 7585
University of North Carolina at Chapel Hill
Chapel Hill, NC  27599-7585

Phone: (919) 966-8012
Email: bea...@med.unc.edu
Website: http://hsl.lib.unc.edu
__________________________________________________

Connecting people everywhere with knowledge to improve health



-----Original Message-----
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Kyle 
Breneman
Sent: Tuesday, June 28, 2016 7:28 AM
To: CODE4LIB@LISTSERV.ND.EDU
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?

Regards,
Kyle

Reply via email to