Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Add Regular Expression-type feature to Processing Rules

Avatar

Avatar
Ignite 1
Level 9
ericmatisoff1
Level 9

Likes

356 likes

Total Posts

154 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Give Back
Validate 1
Boost 50
Boost 5
View profile

Avatar
Ignite 1
Level 9
ericmatisoff1
Level 9

Likes

356 likes

Total Posts

154 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Give Back
Validate 1
Boost 50
Boost 5
View profile
ericmatisoff1
Level 9

20-07-2011

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 Comments

Avatar

Avatar
Applaud 5
Level 1
jonnycarroll
Level 1

Likes

0 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Applaud 5
View profile

Avatar
Applaud 5
Level 1
jonnycarroll
Level 1

Likes

0 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Applaud 5
View profile
jonnycarroll
Level 1

27-06-2012

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.

Avatar

Avatar
Level 1
michaeldrayson6
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
michaeldrayson6
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
michaeldrayson6
Level 1

27-06-2012

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

Avatar

Avatar
Ignite 1
Level 9
ericmatisoff1
Level 9

Likes

356 likes

Total Posts

154 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Give Back
Validate 1
Boost 50
Boost 5
View profile

Avatar
Ignite 1
Level 9
ericmatisoff1
Level 9

Likes

356 likes

Total Posts

154 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Give Back
Validate 1
Boost 50
Boost 5
View profile
ericmatisoff1
Level 9

27-06-2012

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

Avatar

Avatar
Boost 5
Level 2
jmoorman2
Level 2

Likes

14 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Boost 5
Level 2
jmoorman2
Level 2

Likes

14 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
View profile
jmoorman2
Level 2

01-07-2012

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