Managing properties and views
While you might think about your website or mobile app as a distinct, real-world piece of property, like a storefront, Google Analytics understands a property only as a resource associated with your tracking code. When you track a resource using Google Analytics, you include a property ID in the tracking code that you put on your web pages or in your app source code. Performance data, like number of visitors or screen views, for resources tagged with the same ID is collected into the corresponding property.
For example, if you associate one property ID with two websites, data for both websites appears in the same property in your Google 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.
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.
While it’s possible to combine several resources into one property if you tag them with the same tracking code and property ID, web and app resources cannot be mixed into the same property: web-tracking data can only appear in designated web properties, and app-tracking data can only appear in designated app properties. Alternative configurations are not supported and result in corrupt or incomplete data. If you’re tracking mobile apps, consult our best practices for mobile app analytics.