Advanced Segments Vs. Profiles & Filters

October 30, 2008 | Jonathan Weber

Google announced lots of new features last week, and one of the most exciting is Advanced Segments. There are already some great posts out there in the analytics blogosphere explaining what Advanced Segments are all about and how to use them (here’s one from Justin Cutroni, and one from Avinash Kaushik). But we wanted to take a few minutes to compare and contrast using Advanced Segments vs. using profiles and filters to get a different view of the same site.

Up until now, there were some reports in Google Analytics, like the Visitor Loyalty reports and the Funnel Visualization report, that you could only segment by creating a new profile for your site with filters on it to get just the traffic you want. For example, do you want to see the Visitor Loyalty report just for your paid search visitors? Create a profile that only includes your paid search traffic. We’ve done lots of posts about filters in the past detailing how they work to set up exactly these kinds of things.

With Advanced Segments, though, many of these reports can be segmented. Here’s a screenshot of a segmented Visitor Loyalty report. (The Funnel Visualization report, sadly, remains un-segmentable.)

visitor-loyalty-google-analytics1

And the real upshot of using Advanced Segmentation is, you can look back historically on the data! With profiles and filters, the changes you make only have an effect from the time you make the change going forward. With Advanced Segmentation, the report instantly shows you the segments for the historical data you have.

Advanced Segmentation has several other advantages as well. You can see multiple advanced segments simultaneously in the same report.

all-traffic-sources-google-analytics

You can also create advanced segments that wouldn’t have been easy or even possible with filters, such as segments for visits with metrics in a certain range (more than 3 pageviews, more than 2:00 on site, and so on).

all-traffic-sources-google-analytics2

And finally, the interface for creating advanced segments is much more intuitive than creating filters — you don’t necessarily need to understand regular expression to create most advanced segments you can dream up.

So given all this, who even needs to use profiles and filters any more? Forget them! Well, not exactly. There are still several very good reasons for using profiles and filters. One is for kinds of traffic you almost always want to exclude from your reports, such as internal traffic from your organization to your website (you don’t want your employees counted as visitors in most cases — and IP address isn’t a dimension you can use for creating Advanced Segments anyway). You’ll also still want additional profiles to handle more than four goals. And lastly, you can manage access to profiles with the User Manager, so it’s easy to keep track of who can see which sets of data — you can assign different users to different profiles as either read-only users or administrators. (Advanced Segments, on the other hand, are tied to a particular user’s login, like the Dashboard or email preferences. Each user has their own set of Advanced Segments that are available on whatever accounts or profiles they have access to.)

So here’s a summary of the differences between the two approaches…

Advanced Segments:

  1. Segment previously un-segmentable reports (except Funnel Visualization), including historic data.
  2. See multiple advanced segments at once in the same report.
  3. Types of segmentation that weren’t possible with filters: visits with conversion, visits with more than 3 pageviews, visits that spent more than 2:00 on the site, etc.
  4. More intuitive to set up for non-technical users.
  5. Tied to a user login.

Filters & Profiles:

  1. Still useful for filtering certain kinds of traffic you almost always want to exclude, like your internal traffic.
  2. Segment the Funnel Visualization report.
  3. Use multiple profiles for more than four goals.
  4. Tied to the Google Analytics account, manage access with the User Manager.

– Jonathan