Project-Level Filters

Project-level filters are shared filters that apply to an entire Search Analytics or User Analytics project.

Regular view filters apply only to the saved view where they are configured. A project-level filter is applied first to all data in the project. Each view’s filters are then applied on top of it.

When to Use Them

Use a project-level filter when you want the whole project to focus on a fixed analysis scope.

Analyze only a specific directory or URL area.
In Search Analytics, focus on specific queries or search types.
In User Analytics, focus on specific landing pages, traffic sources, or devices.
Avoid repeating the same scope condition in every view.

For example, if you create a project for analyzing only recruiting pages within one site, set the recruiting page URL condition as the project-level filter. Every view in that project will then be scoped to recruiting pages.

Configure a Project-Level Filter

Open the target Search Analytics or User Analytics project.
Open the project settings.
In “Project-level filter,” select “Edit project-level filter.”
Select conditions from “Add filter.”
Review the conditions and select “Save.”

Configured filters are shown on the same settings page. On analysis pages, they appear as “Project-level filter (applied automatically)” so you can distinguish them from regular view filters.

Search Analytics Conditions

In Search Analytics, you can apply these conditions across the project:

Query
URL
Search type
Device
Country
Search Appearances
Anonymous query

For query and URL conditions, you can use the same match types as regular view filters.

User Analytics Conditions

In User Analytics, you can apply these conditions across the project:

Landing page
Second page
Landing page title
Second page title
Devices
OS
Browsers
Default channel group
Sources
Mediums
Campaigns
Country, region, and city
Surf
Page Location Count
Session Number
AB Testing

Notes

A project-level filter affects every view and aggregation in the project. If you only want to filter one view, use a regular view filter instead.

Project-level filters support fewer fields than regular view filters. In Search Analytics, “Query group” and “URL group” are not available. In User Analytics, “Visited Page,” “Revenue,” “User ID,” “Session ID,” “Custom channel group,” “Events,” “Events to Exclude,” “Landing page URL group,” and “Second page URL group” are not available.

In User Analytics, saving a project-level filter reprocesses the project’s data so the filter can be applied. Reports may be temporarily unavailable until this finishes, but no data is lost.

To remove the filter, select “Clear filter” in the project settings.

Workspaces / Projects / Views

Using Search Analytics

Using User Analytics