In a Google Analytics 4 property, the default regex is a "full match." The data must exactly match the pattern you provide. Tips Default behavior between Universal Analytics and Google Analytics 4īy default, regular expressions in Universal Analytics properties are treated as a "partial match." The expression will be true if the pattern you provide is contained anywhere in the data.įor example, if you provide the pattern "India" the regex matches "India", "Indian", "Indiana", "Indianapolis", and so on. You don't need to use metacharacters to achieve this partial match. indicates that the adjacent dot should be interpreted as a period or decimal rather than as a wildcard. Indicates that the adjacent character should be interpreted literally rather than as a regex metacharacter Matches the enclosed characters in any order anywhere in a stringĬreates a range of characters within brackets to match anywhere in a string Matches the enclosed characters in exact order anywhere in a string Matches the adjacent characters at the end of a string Matches the adjacent characters at the beginning of a string Matches the preceding character 0 or more times Matches the preceding character 1 or more times Matches the preceding character 0 or 1 times Matches any single character (letter, number or symbol) Or if you wanted to create a view filter that included only campaign data from two different cities, you could create a regular expression like San Francisco|New York (San Francisco or New York).
Rather than enter 25 different IP addresses, you could create a regular expression like 198\.51\.100\.\d* that matches the entire range of addresses. In the context of Analytics, regular expressions are specific sequences of characters that broadly or narrowly match patterns in your Analytics data.įor example, if you wanted to create a view filter to exclude site data generated by your own employees, you could use a regular expression to exclude any data from the entire range of IP addresses that serve your employees. Return str.replace(/*+?.This article covers regular expressions in both Universal Analytics and Google Analytics 4. If you create a regular expression on the fly from a user-supplied string, you can use the following function to properly escape the special characters: This feature is specific for JavaScript lone closing brackets are allowed in other languages. Lone closing brackets ] and } are allowed by default, but if you use the 'u' flag, then you must escape them: In JavaScript, you also need to escape the slash / in regular expression literals: Alternatively, you can escape the caret: JavaScript For example: means "any character except vowels", while means "any vowel or a caret". If you need to include the caret ^ into a character class, it cannot be the first character otherwise, it will be interpreted as any character except the specified ones. If you need to include the dash into a character class, you can make it the first or the last character instead of escaping it. Inside character classes, you must escape the following characters:įor example, to find an opening or a closing bracket, use ]. If you want to find the backslash itself, double it: \\. For example, to find the text $100, use \$100. If you want to find one of these metacharacters literally, please add \ before it. In most regular expression engines (PCRE, JavaScript, Python, Go, and Java), these special characters must be escaped outside of character classes: Which special characters must be escaped in regular expressions?
0 kommentar(er)
