Expand my Community achievements bar.

SOLVED

Processing Rules: examples of rules that would contradict each other

Avatar

Level 1

Hi!

 

Wondering if anyone is able to help out with some knowledge transfer on Processing Rules. I've looked into several links that are available online about them but was still left with some questions.

 

Does anyone have an example of how processing could potentially be set up to contradict each other? 

 

Any videos or more links are helpful. Here are the below I have seen so far (basically the Adobe provided info) :

https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/processing-rules/processing-rules...

https://docs.adobe.com/help/en/analytics/admin/admin-tools/processing-rules/processing-rules-configu...

https://docs.adobe.com/help/en/analytics/admin/admin-tools/processing-rules/processing-rules-example...

https://docs.adobe.com/help/en/analytics/admin/admin-tools/processing-rules/processing-rules-example...

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 3

Hi @paulinaMB ,

 

If I have correctly understood, you are looking for an example about how a processing rule setup could contradict each other.

This can happen if you have multiple processing rules setup to overwrite value of same variable.

For example, Rule#1 is setting up an evar1 with a value, now there is another rule#5 setup which is again setting up a value in an evar1. In this case the latest rule will take the precedence, evar1 will have value which was set via rule#5.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 3

Hi @paulinaMB ,

 

If I have correctly understood, you are looking for an example about how a processing rule setup could contradict each other.

This can happen if you have multiple processing rules setup to overwrite value of same variable.

For example, Rule#1 is setting up an evar1 with a value, now there is another rule#5 setup which is again setting up a value in an evar1. In this case the latest rule will take the precedence, evar1 will have value which was set via rule#5.