-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Joel
Marchesoni
Sent: Thursday, October 17, 2013 9:08 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Google Analytics on multiple systems
Oh wow, sorry, that's not right. I was thinking 25; not sure where the 4
Hi Joel,
It usually ends up being easiest to go with one GA account, separating
different sources by using different properties (e.g., UA-[acct number]-1
for CONTENTdm, UA-[acct number]-2 for LibGuides, etc.) rather than separate
accounts entirely. Each property can have different users with
@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Google Analytics on multiple systems
Hi Joel,
It usually ends up being easiest to go with one GA account, separating
different sources by using different properties (e.g., UA-[acct number]-1 for
CONTENTdm, UA-[acct number]-2 for LibGuides, etc.) rather than
[mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Josh Wilson
Sent: Thursday, October 17, 2013 10:24
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Google Analytics on multiple systems
Hi Joel,
It usually ends up being easiest to go with one GA account, separating
different sources by using different
: [CODE4LIB] Google Analytics on multiple systems
Wow, 250,000? I'm not sure that's right, though I'm prepared to believe
anything. I checked the GA documentation, which says you can officially have 50
profiles per account. Each property has at least one default profile, so that's
probably the official
Hello,
We currently have Google Analytics on our main library pages and digital
collections pages on the same domain. Now that CONTENTdm has a GA easy button
we are going to add Analytics to it as well, and while we're at it probably
LibGuides and non-authenticated ILLiad pages (I mainly want
Hello Joel and all,
We customized one dashboard that forced all of our vended products to
identify into one singular dashboard and then tease them out with filters
(sort of like this presentation
http://conferences.infotoday.com/documents/158/B104_Hess.pdf) . I didn't
like that, so we using the
