GTM Regex Generator

Why Regex Is Essential in Google Tag Manager

Regular expressions — regex — are one of the most powerful tools in any GTM practitioner's toolkit. In GTM, regex enables you to write a single trigger condition that matches hundreds or thousands of URLs, rather than creating individual triggers for each page. A single regex pattern like /checkout/(cart|payment|confirmation) can replace three separate triggers, making your GTM container cleaner, more maintainable, and less prone to configuration drift over time.

This GTM regex generator eliminates the need to memorise regex syntax. Describe your matching requirement — a URL pattern, a page path, a query string condition — and the tool builds and tests the correct pattern instantly, ready to paste directly into a GTM trigger condition field.

Where GTM Uses Regex

GTM supports regex matching in several key places: Trigger conditions using "matches RegEx" or "matches RegEx (ignore case)" for Page URL, Page Path, Click URL, and any other variable value; RegEx Table variables that map input values to output labels (e.g. mapping URL paths to page category names); and Lookup Table variables that can use regex matching to find the right output row. Understanding which trigger variables support regex and which require exact matches is the first step to using it effectively.

GTM Regex Patterns You'll Use Every Day

These are the most commonly needed GTM regex patterns and when to use them:

• Thank-you page match: /thank-you|/order-confirmation|/success — fires on any purchase confirmation URL variant.
• Starts with path: ^/blog/ — matches any URL path that starts with /blog/, useful for firing a GA4 tag only on blog posts.
• Query string contains: [?&]source=email — matches URLs where the query string includes a specific UTM parameter.
• Exclude admin pages: ^(?!/admin/) — negative lookahead to exclude all admin URLs from a trigger.
• Match specific product categories: /products/(shoes|bags|accessories)/ — fires only on specific product category pages.

Testing Regex Before Deploying to GTM

Never deploy a regex trigger to GTM without testing it first. A regex that matches too broadly will cause tags to fire on unintended pages — potentially sending purchase events on product pages, or contact events on every page load. Use this GTM regex generator to test your pattern against representative sample URLs from your site before copying it into GTM. Also test in GTM Preview mode after deployment to confirm the trigger only fires on the intended pages and not on any others. A well-tested regex trigger prevents months of bad data collection.