<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later</title>
	<atom:link href="http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html</link>
	<description>Canada's Search and Social Media Authority</description>
	<lastBuildDate>Tue, 14 Feb 2012 08:57:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Tim Schneider</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-40590</link>
		<dc:creator>Tim Schneider</dc:creator>
		<pubDate>Mon, 22 Nov 2010 22:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-40590</guid>
		<description>I think I get where you&#039;re going - but the diagram was confusing.

In my example, consultantA@gmail.com is limited to 50 accounts under GA, which is why we never create the account in GA. The client creates the account and adds consultantA@gmail.com as admin.

I picture it with the client account on top, with &#039;Your account&#039; added to each one as admin.</description>
		<content:encoded><![CDATA[<p>I think I get where you&#039;re going &#8211; but the diagram was confusing.</p>
<p>In my example, <a href="mailto:consultantA@gmail.com">consultantA@gmail.com</a> is limited to 50 accounts under GA, which is why we never create the account in GA. The client creates the account and adds <a href="mailto:consultantA@gmail.com">consultantA@gmail.com</a> as admin.</p>
<p>I picture it with the client account on top, with &#039;Your account&#039; added to each one as admin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helen</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-40582</link>
		<dc:creator>Helen</dc:creator>
		<pubDate>Mon, 22 Nov 2010 21:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-40582</guid>
		<description>Hi Tim, 

Thanks for your comment- we&#039;re saying exactly the same thing... set up a new GA account for every new client, and you silo the accounts from one another. You don&#039;t need to make the new client account tied to your personal accounts - just give admin access to the person generating the analysis or reports for your clients. 

BTW - if you set up every new client as a new GA account, you won&#039;t get capped out at 50 new accounts, because you&#039;ll be creating them as separate accounts, and just tying them together with admin access in your one &quot;reporting&quot; account. 


Paul - to &quot;unhook&quot; an account, simply remove their GA access as a &quot;User&quot; or an &quot;Administrator&quot;. Now only you can access their account, and they can&#039;t. Or if you are handing the account to someone else, they simply remove you as a user - now you can&#039;t access their accounts - the account is &quot;unhooked&quot; from you.</description>
		<content:encoded><![CDATA[<p>Hi Tim, </p>
<p>Thanks for your comment- we&#039;re saying exactly the same thing&#8230; set up a new GA account for every new client, and you silo the accounts from one another. You don&#039;t need to make the new client account tied to your personal accounts &#8211; just give admin access to the person generating the analysis or reports for your clients. </p>
<p>BTW &#8211; if you set up every new client as a new GA account, you won&#039;t get capped out at 50 new accounts, because you&#039;ll be creating them as separate accounts, and just tying them together with admin access in your one &#034;reporting&#034; account. </p>
<p>Paul &#8211; to &#034;unhook&#034; an account, simply remove their GA access as a &#034;User&#034; or an &#034;Administrator&#034;. Now only you can access their account, and they can&#039;t. Or if you are handing the account to someone else, they simply remove you as a user &#8211; now you can&#039;t access their accounts &#8211; the account is &#034;unhooked&#034; from you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Schneider</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-40561</link>
		<dc:creator>Tim Schneider</dc:creator>
		<pubDate>Mon, 22 Nov 2010 19:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-40561</guid>
		<description>Have to disagree with the idea here.

In our experience, it is best to:

1.) Have the client create a generic gmail account for the company. This way, there is nothing tied to personal accounts. clientA@gmail.com

2.) Consultant/Agency should also have a generic account consultantA@gmail.com

3.) Provide the client with instructions on how to create a GA account and how to add consultantA@gmail.com admin access.


This set up has a number of benefits:

1.) Consultant will not run out of accounts in GA at 50 (happened to us) and can access set up and all admin features of clientA account

2.) Each client now has 50 accounts plus all the profiles under each account to work with.

3.) Client has control of GA access. Can stop consultant A from seeing data and add consultant B at any time.

4.) With no GA accounts tied to personal accounts, risk of losing access to data when someone leaves (happened to us) is mitigated.</description>
		<content:encoded><![CDATA[<p>Have to disagree with the idea here.</p>
<p>In our experience, it is best to:</p>
<p>1.) Have the client create a generic gmail account for the company. This way, there is nothing tied to personal accounts. <a href="mailto:clientA@gmail.com">clientA@gmail.com</a></p>
<p>2.) Consultant/Agency should also have a generic account <a href="mailto:consultantA@gmail.com">consultantA@gmail.com</a></p>
<p>3.) Provide the client with instructions on how to create a GA account and how to add <a href="mailto:consultantA@gmail.com">consultantA@gmail.com</a> admin access.</p>
<p>This set up has a number of benefits:</p>
<p>1.) Consultant will not run out of accounts in GA at 50 (happened to us) and can access set up and all admin features of clientA account</p>
<p>2.) Each client now has 50 accounts plus all the profiles under each account to work with.</p>
<p>3.) Client has control of GA access. Can stop consultant A from seeing data and add consultant B at any time.</p>
<p>4.) With no GA accounts tied to personal accounts, risk of losing access to data when someone leaves (happened to us) is mitigated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin Jones</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-25864</link>
		<dc:creator>Kelvin Jones</dc:creator>
		<pubDate>Wed, 15 Sep 2010 14:58:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-25864</guid>
		<description>Quite frankly Google really messed this one up.... you should be able to add sites under one account then just let users/clients have administrator rights to their own sites and not let administrators see all sites. Even a mid teir would help something like &#039;power user&#039; where they can set goals, filters and the likes. &#039;Admin&#039; is for the webmaster, &#039;Power User&#039; for the clients web team and &#039;User&#039; for third-parties and general staff that need the data only.</description>
		<content:encoded><![CDATA[<p>Quite frankly Google really messed this one up&#8230;. you should be able to add sites under one account then just let users/clients have administrator rights to their own sites and not let administrators see all sites. Even a mid teir would help something like &#039;power user&#039; where they can set goals, filters and the likes. &#039;Admin&#039; is for the webmaster, &#039;Power User&#039; for the clients web team and &#039;User&#039; for third-parties and general staff that need the data only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Analytics Profile Architecture for Dummies &#124; Search Engine People Blog</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-14341</link>
		<dc:creator>Google Analytics Profile Architecture for Dummies &#124; Search Engine People Blog</dc:creator>
		<pubDate>Fri, 20 Nov 2009 14:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-14341</guid>
		<description>[...] the whole series: #1 How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later #2 Google Analytics Profile Architecture for Dummies #3 Google Analytics Filter Best [...]</description>
		<content:encoded><![CDATA[<p>[...] the whole series: #1 How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later #2 Google Analytics Profile Architecture for Dummies #3 Google Analytics Filter Best [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Analytics Filter Best Practices &#124; Search Engine People Blog</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-14340</link>
		<dc:creator>Google Analytics Filter Best Practices &#124; Search Engine People Blog</dc:creator>
		<pubDate>Fri, 20 Nov 2009 14:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-14340</guid>
		<description>[...] the whole series: #1 How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later #2 Google Analytics Profile Architecture for [...]</description>
		<content:encoded><![CDATA[<p>[...] the whole series: #1 How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later #2 Google Analytics Profile Architecture for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-13725</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 04 Nov 2009 05:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-13725</guid>
		<description>How do you &quot;unhook&quot; a client account set up this way?</description>
		<content:encoded><![CDATA[<p>How do you &#034;unhook&#034; a client account set up this way?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DR. WHAW? Sunday Digest &#8211; Week-ending October 25, 2009 &#171; One true sentence.</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-13367</link>
		<dc:creator>DR. WHAW? Sunday Digest &#8211; Week-ending October 25, 2009 &#171; One true sentence.</dc:creator>
		<pubDate>Mon, 26 Oct 2009 01:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-13367</guid>
		<description>[...] How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later by Helen Overland &#8212; Having a Google Analytics account in the first place is a huge step in [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later by Helen Overland &#8212; Having a Google Analytics account in the first place is a huge step in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DR. WHAW? &#8211; October 22, 2009 &#171; One true sentence.</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-13350</link>
		<dc:creator>DR. WHAW? &#8211; October 22, 2009 &#171; One true sentence.</dc:creator>
		<pubDate>Fri, 23 Oct 2009 23:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-13350</guid>
		<description>[...] 1. How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later by Helen Overland &#8212; Having a Google Analytics account in the first place is a huge step in the right direction, but I love this overview of how to set up your account.  It will seriously help you make sure that you set your goals ahead of time and make sure you don&#8217;t end up confused.  I really strongly recommend this article if you&#8217;re considering using Google Analytics (and you should be) to measure campaigns or your work. [...]</description>
		<content:encoded><![CDATA[<p>[...] 1. How to Set Up Your Google Analytics Account Structure to Avoid Headaches Later by Helen Overland &#8212; Having a Google Analytics account in the first place is a huge step in the right direction, but I love this overview of how to set up your account.  It will seriously help you make sure that you set your goals ahead of time and make sure you don&#039;t end up confused.  I really strongly recommend this article if you&#039;re considering using Google Analytics (and you should be) to measure campaigns or your work. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helen Overland</title>
		<link>http://www.searchenginepeople.com/blog/how-to-set-up-your-google-analytics-account-structure-to-avoid-headaches-later.html#comment-13335</link>
		<dc:creator>Helen Overland</dc:creator>
		<pubDate>Fri, 23 Oct 2009 15:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=5104#comment-13335</guid>
		<description>You&#039;re welcome!</description>
		<content:encoded><![CDATA[<p>You&#039;re welcome!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

