Refine GA4 advanced matching follow-up UX []#10955
Open
zacharyyankiver wants to merge 9 commits into
Open
Conversation
- Added advanced path pattern support for building GA4 page paths from selected entry fields.
- Added integer fields as valid substitutions in advanced path patterns, while keeping the standard Slug field dropdown limited to short text fields.
- Added {locale} support, including sidebar locale selection when a configured pattern uses {locale}.
- Updated sidebar locale behavior to default from editor, active, or default locale and display locale options alphabetically.
- Changed wildcard syntax from .* to *, with helper copy explaining wildcard path matching.
- Removed literal vs regex matching in favor of simpler wildcard guidance.
- Added validation that selected entry fields must appear as substitution tags in the pattern.
- Removed unknown-variable validation so literal brace URL segments are allowed.
- Cleaned up config screen copy across intro, advanced matching, field selection labels, trailing slash copy, Slug field tooltip, and Advanced tooltip.
- Cleaned up sidebar UX by improving error messaging, removing Undetermined metric, adjusting the custom date modal, and removing redundant custom date display text.
Ben Golden (lambardi)
changed the title
Contributor
Author
|
Ben confirmed in Slack that the current unknown-variable validation is intentional: arbitrary {...} brace segments should be rejected so the app can keep meaningful validation around selected substitution fields. I validated /docs/{literal}/{slug}/ and confirmed the config correctly shows an unknown variable error for {literal}. The commit message note about allowing literal brace URL segments is outdated, but the implementation behavior is expected. |
Mitch Goudy (mgoudy91)
approved these changes
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation