What Are Views in Google Analytics?

If you've spent any time with older versions of Google Analytics, you’ve likely come across the term "View." It was the fundamental level where you analyzed your reports and data. With the switch to Google Analytics 4, however, Views have disappeared, leaving many users wondering how to organize their data. This article will explain what Views were in Universal Analytics, why they were so useful, and how you can achieve the same goals using the new tools available in GA4.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What Exactly Were Views in Universal Analytics?

In Universal Analytics (UA), your account was structured in a clear hierarchy: Account > Property > View.

• Account: The highest level, representing your company or organization.
• Property: A specific website, app, or blog that you wanted to track (e.g., www.yourstore.com).
• View: A defined perspective of the data from a single property. Think of it as a filtered lens through which you looked at your website's performance.

You could have multiple Views under a single Property, each with its own unique configuration, filters, and goals. This allowed you to segment and protect your data without altering the raw data stream coming into your Property. Once data was collected and processed for a View based on its settings, that instance of the data was permanent. If a filter excluded certain traffic, that traffic was gone from that View forever.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Common Types of Views Used in Universal Analytics

Because of this permanence, it became a best practice to create at least three standard Views for any new property:

1. The Raw Data View: This was the most critical View and your ultimate safety net. It contained absolutely no filters, no goals, and no modifications. It was a pure, unaltered backup of every single hit sent to your property. If you ever misconfigured a filter in another View and accidentally excluded important traffic, this raw data View was the only place you could go to see what you had missed.

2. The Master (or Primary) View: This was the View you and your team would use for day-to-day reporting and analysis. It included essential filters to clean up the data, such as excluding internal traffic from your office IPs, filtering out bot traffic, or forcing all URLs to lowercase to prevent duplications. This was your "single source of truth" for performance reporting.

3. The Test View: This was your sandbox. Before applying a new, potentially complex filter to your Master View, you would first implement it in the Test View. This allowed you to see its impact on a small subset of data without risking the integrity of your primary reports. You could freely experiment with advanced regular expressions, new goals, or events here, knowing that any mistakes wouldn't corrupt your historical data in the Master View.

Other Specialized Views

Beyond the standard three, teams often created specialized Views for specific reporting needs, such as:

• Subdomain Views: A filter to only include traffic to blog.yourwebsite.com, separating it from the main site.
• Geographic Views: Views that only showed data for users from a specific country or region, perfect for international marketing teams.
• Campaign-Specific Views: Highly filtered views to isolate traffic from a single major marketing campaign.
• Mobile vs. Desktop Views: Using filters to create separate reports based on the user's device category.

The Big Shift: Views Are Gone in Google Analytics 4

When you set up a new Google Analytics 4 property, you'll immediately notice the hierarchy has changed. It's now simply Account > Property. Data from various sources — your website, iOS app, or Android app — flows into the Property through something called "Data Streams."

So, why did Google get rid of Views? The reason lies in GA4's fundamentally different, event-based data model. Unlike UA, which was built around sessions and pageviews, GA4 is designed to provide a more unified understanding of the user journey across multiple platforms. In this new, flexible model, the concept of a rigid, permanently filtered View is replaced by more dynamic, on-the-fly methods of data segmentation.

The core philosophy has shifted from creating separate, pre-filtered reporting silos (Views) to collecting a single, unified stream of raw data that you can segment and analyze in countless ways directly within the reporting interface.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How to Replicate View Functionality in GA4

Switching to a "View-less" world doesn't mean you've lost the ability to organize and clean your data. GA4 provides several powerful tools to achieve the same result, albeit with a different workflow.

1. How to Replicate an "IP Filtered" View

Excluding internal traffic is one of the first things every analyst does. In GA4, this is handled through Data Filters.

• Go to Admin (the gear icon in the bottom left).
• In the Property column, click on Data Streams and select your web stream.
• Scroll down and click on Configure tag settings.
• Click Show More and then select Define internal traffic.
• Create a rule to define your office or internal IPs. Give it a name like "Office IP Addresses" and add the IP addresses you want to exclude. GA4 will automatically start adding a parameter (traffic_type='internal') to events coming from those IPs.
• Now, go back to Admin > Data Settings > Data Filters. You'll see an "Internal Traffic" filter that is in "Testing" mode. Click on it and change its state to "Active."

After activating it, GA4 will now automatically exclude this internal traffic from your standard reports, effectively creating your "Master View."

2. How to Replicate a "Raw Data" and "Test" View

Since data filters in GA4 permanently alter the data that's processed (just like in UA Views), you still need a way to maintain a true raw data backup and a safe place to test. The best practice for this is to create separate GA4 properties.

• For Raw Data: Create a second GA4 property (e.g., "YourStore - Raw Data Backup") and install the tag on your site alongside your primary property tag. Do not configure any filters or settings on this property. It will serve as your untouched backup.
• For Testing: Create a third GA4 property (e.g., "YourStore - Dev/Test") for testing new event tracking, custom dimensions, or filter configurations before rolling them out to your primary property.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

3. How to See Data for a Specific Subdomain, Country, or Device

This is where GA4's reporting interface really shines. Instead of pre-filtered Views, you use Comparisons and Audiences.

Using Comparisons

Comparisons allow you to apply temporary segments to almost any standard report.

Let's say you want to see data only for your blog. In a report like the Traffic acquisition report, click "Add comparison" at the top.

• Set the Dimension to "Hostname."
• Set the Match Type to "exactly matches."
• Set the Value to "blog.yourwebsite.com."
• Click Apply.

The entire report instantly updates to show you data only from that subdomain, just like a Subdomain View would have. You can add up to four comparisons at once to analyze different segments side-by-side.

Using the Explore Hub

For more permanent or complex reports, use the Explore section. Here, you can build custom free-form reports, funnels, and path explorations. Any segments or filters you apply to an Exploration can be saved, so you can return to that specific report whenever you need it without rebuilding it. This is the closest equivalent to having a persistently saved, custom "View" of your data.

Using Audiences

Audiences allow you to group users together based on their behavior, attributes, or the events they trigger. For instance, you can create an Audience of "Users from Canada" or "Users who visited the blog." Once created, you can use these Audiences in your Comparisons and Exploration reports to analyze the behavior of specific user groups over time.

Final Thoughts

While the elimination of Views in Google Analytics 4 can feel jarring at first, it represents a strategic shift toward more flexible, user-centric data analysis. Universal Analytics relied on creating rigid, pre-filtered Views for segmentation, but GA4 encourages a more dynamic approach where you slice and dice a complete dataset on the fly using powerful tools like Comparisons, Explorations, and Audiences.

Getting your team comfortable with this new way of analyzing data can be a challenge. Instead of wrestling with GA4 interfaces to create the reports you need, tools like Graphed are here to help. We connect directly to your Google Analytics 4 property and let you build dashboards and get insights simply by asking questions in plain English. Want to see sales filtered by campaigns targeting Canada? Just ask, and we'll create the report for you instantly, without you needing to configure a single comparison or filter in GA4.