SEO Gets
Analytics

Why can I see my GA4 data in the dashboard but not in the filtered view?

You're seeing your GA4 data in the main dashboard, but when you click into a group or apply a filter, the numbers disappear or look much lower than expected. This is usually caused by how GA4 stores URLs—and how your regex filters are written to match them.

GA4 only stores URL paths, not full URLs

When you view GA4 data in the main dashboard, SEO Gets shows you aggregated data from your GA4 property. But when you click into a group or apply a specific filter, SEO Gets makes a fresh API call to GA4 to fetch detailed data for that subset.

Here's the catch: GA4 doesn't store or return full URLs. Instead of storing:

https://seogets.com/blog

GA4 only provides the path:

/blog

This means if you write a regex filter that tries to match the full URL—like ^https://www or ^https://seogets.com/—it will never match, because GA4 data doesn't include the protocol or domain.

How to fix your regex filters

Write your regex to match the path only, not the full URL. Here are some examples:

  • Incorrect: ^https://seogets.com/blog — matches a full URL that GA4 doesn't store

  • Correct: ^/blog — matches the path that GA4 actually returns

  • Incorrect: https://www\. — tries to match protocol and domain

  • Correct: ^/products/ — matches pages under your products subfolder

The same applies if you're using content groups or filtering by page URL anywhere in SEO Gets—always match the path, not the full URL.

Why this happens

This isn't a bug—it's a GA4 limitation. GA4's Landing Page report and related endpoints return page paths without the domain. This is standard behavior across GA4 integrations, and it's why you might see data in one view that seems to "disappear" when you drill down further.

Quick checklist

  • Check if your filter or regex includes https:// or your domain name

  • Rewrite the regex to start from the path, like ^/blog or /blog

  • Remove any protocol (http, https) or domain references from your filter

If you're still not seeing data after adjusting your filters, it's possible there's simply no matching traffic for the path pattern in the date range you've selected. Try broadening your filter or adjusting your date range to confirm.

Was this helpful?