Processing rules

[priyankagupta20]

How processing rules work?

[kamlesh-maddheshiya · Accepted solution]

The Processing rules let you make changes to data based on defined conditions. When attributes or values match defined conditions, values can be set and deleted, and events can be set.
Rules are applied to all data that comes through
1) AppMeasurement libraries
2) Data Insertion API
3) Full and log data sources
Note: Processing rules do not apply to other data sources.

[Jennifer_Dungan]

Processing rules can also be used to concatenate values, or to assign values such as the User Agent String into a eVar.

But most importantly, Processing Rules are generally needed for Mobile App tracking.. I am not sure about maybe newer Data Stream tracking, but at least traditionally, you cannot set your props and eVars natively in your trackState and trackActions.. you need to set context variables and use Processing Rules to map these to the appropriate dimensions (you can concatenate these values, or map one to one...

This has been the solution since Mobile Services was sunset (and technically before that, as Adobe was cautioning people even back in 2020 that Mobile Service was going to be coming to an end and instructed new Mobile App builds to use Processing Rules rather than become dependent on a tool that would be going away)