What Is an Example of a Property in Google Analytics?

Cody Schneider8 min read

Understanding Google Analytics is a lot like learning basic anatomy - once you grasp the core structure of how everything connects, sorting through your data becomes much more intuitive. One of the foundational building blocks of this structure is the “Property,” a term you need to get comfortable with from day one. This article will explain exactly what a Google Analytics property is, use clear examples to show how to use them, and walk you through getting them set up for your own business.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

First, Understand the Google Analytics Hierarchy

Before defining a property, it helps to see where it fits in the grand scheme of things. Google Analytics organizes your data using a simple three-tiered structure: Account, Property, and View.

Think of it like a filing cabinet system for your business data:

  • The Account is the entire filing cabinet. It’s the highest level and represents your company or overall organization. For instance, "Steve's Shoe Emporium" would be the Account. You can have multiple Accounts under one Google user login.
  • The Property is a drawer within that filing cabinet. Each drawer is designated for a specific digital asset, like a website or a mobile app. Steve might have one drawer labeled "ShoeEmporium.com" (his website) and another labeled "Shoe Emporium Rewards App" (his mobile app). All the data from that website or app goes into its dedicated drawer.
  • The View is a specific folder inside a drawer, containing filtered data. You could have a folder for "All Website Traffic" inside your "ShoeEmporium.com" drawer, another for "USA Sales Traffic Only," and a third for "Traffic Excluding Our Own Office Employees." Views let you look at the same data from different angles.

The hierarchy flows from top to bottom: Account contains Properties, and Properties contain Views. Your data is collected at the Property level, identified by a unique tracking ID.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

So, What Exactly Is a Property?

A Google Analytics Property is a container that holds the data for a single website, mobile app, or other distinct digital asset you want to track. It acts as the central hub where Google collects and processes all analytics data specific to that asset.

When you create a Property, Google Analytics provides you with a unique alphanumeric code called a Measurement ID for Google Analytics 4 (which looks like G-XXXXXXXXXX). You install this ID onto your website or in your app's code. This small piece of code is what allows Google’s servers to recognize user activity from your digital asset and sort it into the correct Property (or "drawer") in your account.

Your business's website will almost always be its own property. So will your mobile app. If your brand operates two different websites for entirely different product lines or regions, those would typically be two separate properties to keep the data clean and independent.

Clear Examples of How to Use Properties

The best way to understand properties is to see them in action. Let’s look at a few common business scenarios and how they would logically set up their Google Analytics structure.

Example 1: The Standard Small Business

  • Business: "CityScape Coffee Roasters," a local coffee shop with a simple e-commerce website where they sell bags of coffee beans.
  • Account: "CityScape Coffee Account"
  • Property 1: "CityScapeCoffee.com"

This is the most common and straightforward setup. One business, one website, one property. All their website traffic data - from homepage visits to online purchases - is collected under this single property.

Example 2: A Company with a Website and an App

  • Business: "FitFusion," a fitness brand that offers online workout videos via its website and a dedicated mobile app for tracking progress.
  • Account: "FitFusion Fitness"
  • Property 1: "FitFusion.com (Web)"
  • Property 2: "FitFusion Mobile App (iOS/Android)"

In this case, the website and the mobile app are two very different user experiences, and they generate different kinds of data. It makes sense to track them in separate Properties. Creating a property for the website gives them data on sign-ups, page views, and session duration. Creating another property for the app gives them data on user retention, screen views, and daily active users. Separating them prevents website data (like blog views) from getting mixed in with app data (like workout completions).

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

Example 3: A Global Corporation with Multiple Websites

  • Business: "GlobalTech Inc.," a large electronics company with distinct websites for the United States, United Kingdom, and German markets.
  • Account: "GlobalTech Inc."
  • Property 1: "globaltech.com (US Website)"
  • Property 2: "globaltech.co.uk (UK Website)"
  • Property 3: "globaltech.de (DE Website)"

Even though it's one global brand, the user bases, languages, currencies, and marketing campaigns for each region are different. Bundling all website data into one giant property would make it very difficult to analyze each market's independent performance. With separate properties, the US marketing team can focus on their .com data, while the German marketing team analyzes the behavior and sales on their .de site without interference.

Example 4: A Brand with Main and Sub-Brands

  • Business: "Outdoor Gear Co.," a company selling various outdoor equipment through its main brand site and operating a separate, specialized blog dedicated to hiking guides.
  • Account: "Outdoor Gear Company"
  • Property 1: "OutdoorGear.com (Main Site)"
  • Property 2: "HikingAdventuresBlog.com (Content Blog)"

Here, the two websites serve different functions. The main site is transactional (e-commerce), while the blog is informational (content marketing). Measuring them in separate properties allows the marketing team to evaluate their performance based on appropriate goals. The Main Site's success might be measured by revenue and conversion rate, whereas the Blog's success is measured by sessions, engagement rate, and newsletter sign-ups.

When Should You Create a New Property?

Use this simple rule of thumb: If you have a separate, standalone digital asset, it generally deserves its own property.

Ask yourself these questions:

  • Does this website or app have a completely separate codebase or domain name? If yes, it’s probably a new property. (e.g., mysite.com and myotherbrand.com should be two properties).
  • Are the user audiences and goals fundamentally different? If you have an e-commerce store and a completely separate customer support portal, they would likely be two properties.
  • Do you need to keep user sessions completely isolated? Data from two different properties cannot be easily combined natively within Google Analytics. Separate properties keep a hard line between data sets.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

How to Create a New Property in Google Analytics 4

Setting up a new property is simple and only takes a few minutes. Here's a quick guide:

  1. Log in to your Google Analytics account.
  2. Click on Admin in the bottom-left corner (it looks like a gear icon).
  3. In the "Account" column, make sure the correct Account is selected.
  4. In the middle "Property" column, click the blue + Create Property button.
  5. Enter a descriptive name for your property (e.g., "Main Company Website" or "iOS App").
  6. Select your reporting time zone and currency. These are important for accurate sales and user timing data.
  7. (Optional) click Show advanced options if you need to create a Universal Analytics property (this is deprecated and not recommended for new setups).
  8. Click Next and fill in some simple business information, like your industry category and business size.
  9. Click Create. You'll now be prompted to set up a "Data Stream." A data stream is essentially the source that sends data into your property. You'll choose one of three options:
  10. Follow the on-screen instructions. For a website, you will enter your URL and stream name. Google will then provide you with your Measurement ID (G-XXXXXXXXXX) and the code snippet to install on your website via Google Tag Manager or by adding it directly to your website's HTML <head> section.

Once the tracking code is properly installed, data will begin flowing into your new property, ready for you to analyze.

Final Thoughts

Understanding a Google Analytics property is a fundamental step toward organizing your data effectively. Think of it as the core container for each of your unique digital assets - whether it’s your main e-commerce website, your mobile app, or a separate marketing blog. Set them up logically from the start, and you’ll save yourself hours of confusion down the line as you start building reports and searching for insights.

Getting your data structured correctly is the first step, but the real goal is getting quick answers from it without the hassle. We found that most people spend hours bouncing between platform-specific tools, wrestling with spreadsheets, and trying to master complex dashboards. That's why we built Graphed. Once you've connected your Google Analytics and other data sources (like Shopify, Facebook Ads, or HubSpot), you can just ask questions in plain English, like "How did last month's blog content affect website conversions?" or "Create a dashboard showing our top traffic sources daily for the last 30 days." We save you the time usually spent on manual reporting so you can get right to making smarter decisions.

Related Articles