Processing Rules and Context Data
Processing rules are used to copy the data you send in context data variables to evars, props, and other variables for reporting.
We recommend grouping your context data variables using "namespaces", as it helps you keep logical ordering. For example, if you want to collect info about a product, you might define the following variables:
"product.type":"hat" "product.team":"mariners" "product.color":"blue"
Context data variables are sorted alphabetically in the processing rules interface, so namespaces let you quickly see variables that are in the same namespace.
We recommend that you avoid naming context data keys using the evar or prop number:
This might make it slightly easier when you perform the one time mapping in processing rules, but you lose readability during debugging and future code updates can be more difficult. Instead, we strongly recommend using descriptive names for keys and values:
Context variables that define counter events should be set to 1:
Context data variables that define incrementor events can have the event as the key and the amount to increment as the value:
Note: Adobe reserves the namespace "a.". Aside from that small restriction, context data variables just need to be unique in your login company to avoid collisions.
Parent topic: Getting Started