Example account structures

Since your account-property-view relationships can take many forms, you'll benefit most by organising them around your personal or business needs.

For example:

  • If you want to collect data for your personal website and personal blog, then you can create one account with two properties, and the necessary views for each property – i.e. one property (and associated views) for your website, and another property (and associated views) for your blog.
  • If you want to collect data for just your company's website, then you can use a single account with that one property, plus one or more views. If there are different departments within your company that want to track their areas of the site separately from one another, then you can create a profile for each of those departments and configure each profile to include only the relevant data.
  • If you manage Analytics for multiple websites that belong to multiple clients, then there are different approaches you can take:
    • Create a separate Analytics account for each client, and as many properties and views as necessary within each account. This type of organisation lets you give your clients access to their Analytics accounts, and ensures that clients are not able to view one another's data.
    • Create one account with separate properties and views for each client. You can restrict user access to the relevant properties and views via permissions. One potential (indeed, potentially catastrophic) downside to this approach is that if you were to subsequently assign permissions to a user at the account level, then that user could then see data for other clients' properties and views in that account.