In Google Analytics, a property is a website, mobile application, or blog, etc., that is associated with a unique tracking ID. A Google Analytics account can contain one or more properties. Learn more about Google Analytics properties. A view is a set of specifications for tracking traffic on a single domain.
For example, if you associate one property ID with two websites, data for both websites appears in the same property in your Analytics account. You can then use views and filters to organize the data. You can segregate the data even further at the report level with tools like Segments.
You can group up to 200 properties into a single aggregate property called a property set. A property set can contain properties of any other type (web pages or apps) except other sets. A property set shows aggregate data for all its member properties. A property set appears in the list of properties for your account.
Basic rules about property sets:
- You cannot add a set as a member to another set, but you can add any other type of verified property.
- You can add only verified properties from your account to a set.
- You must be a verified restricted user (or greater) on all set members in order to access the set.
- If you later lose access to, or verification for, any property in a set, the entire set will become unverified and inaccessible to you. However, data will continue to be collected for the set, and you will be able to see data again as soon as you regain access (or reverify) all set members.
- A set can have only one owner and no users; you cannot share a set with others.
- Sets support some, but not all of, the reports and tools available to other property types.
- Set data is viewable in aggregate only; when viewing impression data for a set that contains properties X, Y, and Z, you are shown the total impressions for X + Y + Z. To see the total impressions for X alone, you must switch to property X in Search Console.
Consider your long-term reporting goals and how they might affect your account structure. Create an implementation plan before you set up new properties. In some cases, you may want to have multiple resources all send data to the same property. In other cases, you may want each resource to send data to a separate property. In either case, you can use views and filters to create specific perspectives of your data.