Your Regex Works in JS but Fails in GA4? Full-Match, RE2, and the Patterns That Actually Work

Count Of Tuscany — Wed, 28 Oct 2026 14:21:57 +0000

You build a regex, test it in your editor, it works. You paste it into a GA4 segment or comparison and... zero rows. No error, no warning, just silence.

Two features of GA4 explain almost every one of these failures.

1. GA4 matches the whole value, not a substring

In JavaScript, /blog/ matches "/blog/my-post" happily. In GA4, filters use full-match semantics: /blog/ matches the value /blog and nothing else.

That's why every GA4 pattern you find in the wild is wrapped in .*:

# matches any page path containing /blog/
.*/blog/.*

Two flavors to remember:

"is one of my regex patterns" (segment dimensions): full match, wrap with .*
"partially matches regex" (some comparison surfaces): substring match, no wrapping needed

Test the exact flavor you'll use - mixing them up is the number one source of "my regex works in the preview but not in the report".

2. GA4 runs RE2, not JavaScript's RegExp

GA4 (like BigQuery, Go, and Rust) uses Google's RE2 engine. RE2 is linear-time - it can never blow up on adversarial input - but that guarantee costs it three PCRE families:

No lookahead / lookbehind: foo(?=bar), (?<=/)(\w+) - rejected
No backreferences: (foo|bar)\1 - rejected
No atomic groups / possessive quantifiers / recursion - rejected

The RE2-friendly mindset:

Instead of	Write
`foo(?=bar)`	`(foo)bar` - capture the part you need
negative lookahead `(?!`	a negated class `[^x]`, or an exclude filter
`(foo	bar)\1`
non-greedy tricks	plain `.*` - GA4 matches the full value anyway

Three patterns that actually work in GA4

Page path filter - all blog posts:

.*/blog/.*

Event name filter - the ecommerce funnel:

(view_item|add_to_cart|begin_checkout|add_payment_info|purchase)

Custom channel grouping - organic social:

.*(facebook|instagram|linkedin|twitter|x\.com|t\.co|youtube).*

(Notice the escaped dot in x\.com - unescaped, it would also match xXcom.)

The workflow that stops the guessing

Write the pattern in a tester that lets you paste your real values (the actual page_path rows, the actual event names - not your memory of them).
Check which engine it targets. JavaScript-valid is not RE2-valid; if your pattern contains (?=, (?! or \1, it will never run in GA4.
Only then paste it into GA4.

I kept failing at step 2 myself, so I built RegexLab - a free, browser-only tester that shows match/no-match per line and keeps the RE2 gotchas visible. There's also a pattern library with tested, copy-paste patterns (dates, URLs, UTM parameters, log levels), each with an RE2-compatibility note, and a dedicated RE2 vs PCRE page listing every unsupported construct with its replacement.

Nothing leaves your browser - the whole thing is client-side JavaScript RegExp under the hood.

TL;DR

GA4 = full match. Wrap substring patterns in .*
GA4 = RE2. No lookahead, no backreferences, no lookbehind
Test against your real data, with the right engine in mind, before you ship the pattern

What's the regex problem that cost you the most debugging time? Mine was a lookahead that silently matched everything in preview and nothing in production.

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

Count Of Tuscany — Sat, 17 Oct 2026 12:28:22 +0000

If you ever pasted a regex into Google Analytics 4 and got zero rows back
while the exact same pattern works fine in your editor — you didn't write a
"wrong" regex. You wrote one that GA4 doesn't run the same way.

Two differences explain almost every failure.

1. GA4 matches the whole string

GA4's regex condition is a full match, not a "contains".

/blog/

In most regex engines, this finds /blog inside /blog/ga4-guide.
In GA4, it matches only the exact string /blog. /blog/ga4-guide → zero rows.

Fix — wrap it:

/blog/.*      → everything under /blog/

.blog.      → any path containing "blog"

GA4 uses RE2 — no lookahead, no backreferences

GA4 runs Google's RE2 engine: fast and safe, but it does not support:

lookahead (?=…) / (?!…)
lookbehind (?<=…) / (?<!…)
backreferences \1

A pattern like ga4(?=-tips) fails silently. And because RE2 can't assert,
"match X but not Y" logic is better expressed as two filters in GA4 itself
(one include, one exclude) instead of one clever regex.

Patterns that actually work in GA4

You want	Regex
Pages under /blog/	`/blog/.*`
Product detail `/products/<slug>`	`/products/[^/]+`
Event ending in `_click`	`.*_click`
Source is google or bing	`(google
URLs with a query string	{% raw %}`.\?.` (use `page_location`, not `page_path`)

Test before you paste

Every pattern above can be checked live against sample data in a free,
browser-only tester — no login, and no data ever leaves your device:

Tester: https://regextester.site/
Cheat sheet, 25+ ready-made GA4 patterns: https://regextester.site/ga4-regex-cheatsheet/

Both run entirely client-side, so what matches in the tester matches in GA4.

DEV Community: Count Of Tuscany