This blog explains why standard filters fail when applied to average position and show you the solution to this common issue.
Filtering on Average Position in Looker Studio with Search Console data can be a bit tricky. If you've tried applying a standard filter to isolate queries or pages with a specific average position, you've likely noticed that it doesn't work as expected. But don’t worry — in this blog, we’ll explain why standard filters fail and show you the solution to this common issue. Let’s dive in!
The issue lies in the Average Position being an aggregated metric — it’s the average ranking of your website for a query or page, based on multiple impressions. When you apply a standard filter in Looker Studio, the filter works at the row level before the metric is aggregated. As a result, your filter doesn’t isolate the rows contributing to the desired Average Position; instead, it may include or exclude data incorrectly. This results in either the 'No data' or the 'Re-aggregating metrics is not supported' message.
There's a simple trick that can we can use to filter on average position using data blending. By blending data, we are able to reaggregate metrics in Looker Studio. This handy feature helps you bypass the limitations of previously aggregated fields, which are automatically set to the AUTO field type. Since you can’t modify this field type or apply additional aggregation functions directly, blending offers an effective workaround.
Follow these steps: