To effectively use processing rules it is essential to understand when they are applied during data collection.
The following tables list the data that is typically available before and after processing rules are applied:
|Dynamic variable lookup||Variables are populated dynamically by pulling information from HTTP headers or other variables. For example,
|AppMeasurement||Functions and plug-ins used in AppMeasurement are executed in the browser or client application.|
|Tag Management||Rules defined in the Data Collection UI are executed as defined.|
|Bot rules||Bot rules let you remove traffic that is generated by known spiders and bots from your report suite.|
|Data added by VISTA||Processing rules are applied before VISTA.|
|Visit page number||As a general rule, processing rules are aware of the data that is contained in the current hit only. Visit page number is compiled after processing rules are applied.|
|Clean URL is added as page name if it is not set||After processing rules and VISTA are applied, the clean URL is added as the page name if there is no page name set. Since this occurs after processing rules are applied, we recommend adding a condition to check if the page name is blank. If you run the Site Content > Pages Report and you see https:// values for page names, it is likely the page name is blank and the URL is being used. You can set up a condition to test for a blank page name, or to test to see if the page name or the page URL contains a specific value. The page name can then be set as needed.|
|Marketing Channel Processing Rules||You can use processing rules to prepare data for processing by Marketing Channel Processing Rules.|
|GEO lookup||This includes the Visitor State and Visitor ZIP/Postal code values.|
|eVars persistence||eVars that were contained in a previous hit are not persisted to each hit during rule processing. Only eVars that are set on the current hit being processed are available.|
If you have a VISTA rule configured to copy hits to another report suite, the hits are sent through any processing rules defined in the other report suite.
If you have processing rules defined on the original report suite, these may or may not be applied based on how the VISTA rule was configured by Engineering Services. To find out, you can ask your implementation specialist if the VISTA rule copies the “pre” or the “post” values to the additional report suite. If the “pre” value is copied, processing rules defined on the original report suite are not applied. If the “post” value is copied, processing rules are applied before the hit is copied.