Hello,
In our setup we have a few accounts, a bunch of properties and many views and it can be a little confusing. What I've noticed when looking at our Google Analytics data is that when we have two properties gathering data under different tracking numbers that those can't be combined in a view and examined together. So: when have our main website under UA-[property number]-1 and our library catalog under UA-[property number]-2, users going from our main website to our catalog look like visitors to UA-[property number]-1 that bounced. I'm not sure how we could get information about the user's path from the website, into the catalog and back again without having them both gathering data under the same property ID. It seems like if they were both the same ID, we would be able to get a lot of information from the Visitors Flow and Entrance Paths.
Does anybody have the reverse-extreme? I mean - one property ID for *everything*, sending the domain to tell the sites apart, split up using views and advanced segments for reporting? I can see some advantages to this method, but in order for it to be successful in not multiple-counting pages with the same path (like /) it seems like we would need to be able to include _setDomainName and _setAllowLinker. Depending on the options provided by our vendor tools, I could see us not having enough customization control over the tracking snippet to do this.
A relatively new change in Google Analytics is that it allows setting permissions at the account, property, or view level. One reason for making multiple accounts in the past was for restricting access, but now that can be controlled at other levels so it makes more sense to have fewer accounts (or even just one account).
-Ginger
-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Joel Marchesoni
Sent: Thursday, October 17, 2013 9:08 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Google Analytics on multiple systems
Oh wow, sorry, that's not right. I was thinking 25; not sure where the 4 zeros came from...
Joel
-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Josh Wilson
Sent: Thursday, October 17, 2013 11:18
To: [log in to unmask]
Subject: Re: [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 limit of properties too, before you'd need to use an extra account. (In turn, you can evidently manage 25 GA accounts per Google user account.)
Not sure where the 250,000 figure comes from, but I've seen a number of scripting workarounds for the profile limit in various analytics blogs, so maybe you can sort of 'overclock' your accounts if you needed to.
On Thu, Oct 17, 2013 at 10:41 AM, Joel Marchesoni <[log in to unmask]>wrote:
> Thank you all for your replies. I'm thinking we'll go with one account
> (we already have a Google account for various other services) with
> multiple properties. One thing that has complicated matters is the
> property we currently use is not yet able to be upgraded to Universal
> Analytics, which is what CONTENTdm uses.
>
> FYI I noticed in my own research that the property limit is 250,000. I
> don't see us hitting that ever...
>
> Joel
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf
> Of Josh Wilson
> Sent: Thursday, October 17, 2013 10:24
> To: [log in to unmask]
> 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 separate accounts entirely. Each property can have
> different users with different permissions levels so you can customize
> who has access to what. You can further refine each property into
> different profiles if you want to filter data from one source in
> different ways. Having everything under one account makes it easy to
> manage and apply common settings (like users, filters, or custom
> reports) between properties and profiles. If you add another user, you only have to add them to one account, too.
>
> There are limits to the number of allowed properties (it's quite high
> and goes up occasionally; not sure what it is offhand), so if you
> bumped into that you could use another GA account. Google has made it
> easier in recent months to jump between accounts and properties, though.
>
> (Sorry for delayed reply, catching up on listservs)
>
>
>
> On Mon, Oct 14, 2013 at 2:36 PM, Joel Marchesoni <[log in to unmask]
> >wrote:
>
> > 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 to see how big a percentage of mobile hits
> > ILLiad
> > gets) as well. I was hoping to hear from the list whether you have
> > all "service points" in one GA account or a separate account for
> > each one,
> and why.
> >
> > Thanks,
> >
> > Joel Marchesoni
> > Tech Support Analyst
> > Hunter Library, Western Carolina University http://library.wcu.edu/
> > 828-227-2860
> > ~Please consider the environment before printing this email~
> >
>
|
