RegEx for processing rules

Avatar

Avatar

tbolle

Avatar

tbolle

tbolle

13-01-2013

You should let us be able to use Regex for setting up conditions for processing rules. We have dynamic URL's and this would make it much easier to to have the rules run correctly.

7 Comments (7 New)
7 Comments

Avatar

Avatar

lucyg98085

Avatar

lucyg98085

lucyg98085

28-01-2013

This would help us also so that we can pull in the value of a subdirectory in a url.

Avatar

Avatar

jnarong

Avatar

jnarong

jnarong

16-03-2015

Within the interface for Processing Rules, it would be great to allow regex conditional statements instead of just the generic ones currently available (contains, equals, does not contain, etc.)

Avatar

Avatar

salernoam29

Avatar

salernoam29

salernoam29

08-08-2016

This would be very useful right now to set one prop equal to part of another.

Avatar

Avatar

BretGundy

Employee

Avatar

BretGundy

Employee

BretGundy
Employee

11-08-2016

We've considered this many times, but have found that a full regex engine could add processing delays. Is it fair to say that the key points of regex are the following?

 

  • Match a pattern, including wildcards, number and alpha-character matching
  • Replace some portion of the string with something
  • Extract a portion of the stirng for use elsewhere

Avatar

Avatar

ericmatisoff

Employee

Avatar

ericmatisoff

Employee

ericmatisoff
Employee

11-08-2016

I'd say it'd be super helpful for IP-based processing rules (a la http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Add-Regular-Expression-type-feature-t o-Processing-Rules/idi-p/5067). The current string-based Processing Rule options make it very difficult to deal with IP ranges.

Avatar

Avatar

joshd7227840

MVP

Avatar

joshd7227840

MVP

joshd7227840
MVP

22-12-2017

bretgundy

There's already an expectation of delay on data availability in reports (except for real-time reports, which let's be honest here, are of limited value to begin with).

Also, I'm pretty sure VISTA rules are able to use regex, yes?

Regex support for various things within AA (filters, segments, PRs, etc.) has been a long-standing request from many people, that other tools (e.g. GA) handle just fine.  The fact that AA continues to have limited to no regex support after all these years is rather mind boggling, and yeah, I'll be the one to address the elephant in the room: the problem isn't with regex: it's with the devs.

Avatar

Avatar

alv123456

Avatar

alv123456

alv123456

23-07-2018

Very important feature missing! Soemtimes we want to remove some specific query string parameters and we cannot do that right now without throwing away the complete query string.