Why Your GA4 Regex Keeps Failing — 2 Rules That Fix 99% of It

If you have copied a regular expression (regex) into Google Analytics 4 (GA4) and received no results while the exact same pattern works in your text editor, it's likely not a mistake in your regex. Instead, the issue lies in how GA4 processes regex. There are two key differences explaining almost all failures.

Firstly, GA4 requires a full match, rather than a "contains" match. In most regex engines, the pattern "/blog" would match "/blog/ga4-guide" as it contains "/blog". However, in GA4, it only matches the exact string "/blog". So, for example, "/blog/ga4-guide" would result in zero rows. To fix this, you can wrap your pattern to ensure a full match, like so: "/blog/.*" for everything under "/blog/" or "blog." for any path containing "blog".

Secondly, GA4 uses RE2 engine, which does not support lookahead assertions, backreferences, or lookbehind assertions. This means patterns like "ga4(?=-tips)" will fail silently in GA4. Instead of trying to force a complex regex, it's better to use two separate filters in GA4: one to include and one to exclude. Patterns that work in GA4 include Pages under "/blog/", Product details under "/products/" with a non-greedy slash, events ending in "_click", and source URLs from Google or Bing.

You can test your regex patterns before pasting them into GA4 using a free, browser-only tester at https://regextester.site/. A cheat sheet with 25+ ready-made GA4 patterns is also available at https://regextester.site/ga4-regex-cheatsheet/. Both tools run entirely client-side, ensuring that what matches in the tester matches in GA4.