Processing rules overview

Processing rules simplify data collection and manage content as it is sent to reporting. Processing rules help simplify interaction with IT groups and Web developers by providing an interface to:

Set an event on the product overview page
Populate campaign with a query string parameter
Concatenate category and page name in a prop for easier reporting
Copy an eVar into a prop to see paths
Clean up misspelled site sections
Pull internal search terms or a campaign ID from the query string into an eVar

Processing Rules Permissions

Administrators have rights to use processing rules by default. Administrators can also grant these rights to non-administrators through the Admin Tools interface. For instructions, see []

Processing rules

Use Context Data to Simplify Data Collection

Context data variables are a type of variable that are available only to processing rules. To use context data variables, key/value data pairs are sent in by your implementation, and processing rules are used to capture these values in standard Analytics variables. This frees programmers from understanding exactly which prop and/or eVar should contain which value.

s.contextData['author'] = "Robert Munch";
s.contextData['section'] = "Books";
s.contextData['genre'] = "Youth";

Once set in code, you can set processing rules to assign values to variables. For example:

Map author to eVar2
Map section to prop1 and eVar3
If author and section exist, set event5

See contextData in the Implement user guide for more information.

Use Processing Rules to Transform Hit Data and Trigger Events

Processing rules can monitor incoming values to transform common typos and set events based on reported data. Props can be copied to eVars. Values can be concatenated for reports, and events can be set.