Add Regular Expression-type feature to Processing Rules | Community
Skip to main content
ericmatisoff1
ericmatisoff1
Level 5
Jul 20, 2011 1:25 PM UTC
New

Add Regular Expression-type feature to Processing Rules

The current features (starts with, contains, ends with, etc) are nice, but having actual Regular Expressions would be even better!

 

If this isn't possible, one great improvement would be to allow for IP Address ranges to be used. For example:

 

Instead of creating a Processing Rule defined as:

Starts with:

129.32.34.15

129.32.34.16

129.32.34.17

129.32.34.18

129.32.34.19

129.32.34.2

Et cetera.



It'd be much more powerful to define the rule as:

129.32.34.15-255

    4 replies

    jmoorman2
    jmoorman2
    Level 2
    Jul 2, 2012 3:18 AM UTC

     I agree.  Providing regex support for processing rules will make this functionality very powerful!

    Translate
    ericmatisoff1
    ericmatisoff1Author
    Level 5
    Jun 28, 2012 6:37 AM UTC

    Thanks for the promotes guys!

     

    Tag Manager needs the same regex support: http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/Add-Regular-Expressions-to-H ost-Match-and-Path-Match-in-Tag/idi-p/6791

    Translate
    michaeldrayson6
    michaeldrayson6
    New Participant
    Jun 28, 2012 3:14 AM UTC

    Couldn't agree more.  Processing rules would be much better with regex support!

    Translate
    jonnycarroll
    jonnycarroll
    New Participant
    Jun 27, 2012 10:16 AM UTC

    Regex capability within processing rules would be very useful and have multiple use cases for us. For example: Creating alternative campaign attribution models. Say you wanted to have a new eVar that will serve as an alternative marketing attribution variable to the "campaign" variable, but not including certain traffic types. The "contains" conditional operator just isn't powerful enough. I want to be able to write a regex against the campaign value to only copy campaign to the new eVar when certain regex conditions are or are not met.

    Translate
    Terms & ConditionsAccessibility statement

    Loading footer...