- Analytics Admin Guide
- Analytics Admin overview
- System requirements
- Admin Tools
- Admin Tools
- Billing
- Bot removal
- Code Manager
- Conversion variables
- Currency codes
- Custom report descriptions
- Customize calendar
- Data Sources
- Default metrics
- Exclude by IP address
- Finding methods
- General Account settings
- Group management
- Internal URL Filters
- Logs
- Marketing Channels
- Menu customizing
- Metric visibility
- App management
- Paid search detection
- Publishing lists
- Publishing Widget
- Preferences manager
- Privacy settings
- Privacy settings
- Processing rules
- Processing rules overview
- Processing rules configuration
- Dimensions available to processing rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Real-time reports
- Scheduled reports queue
- Server-side forwarding
- Simplified reports menu
- Social management
- Success events
- Timestamps optional
- Traffic variables
- Unique Visitor variable
- Video management
- Experience Cloud Admin Console
- Company Settings
- Manage report suites
- User and Product Management (Legacy)
- User and Product Management
- Assign user groups to a report suite
- User management
- User groups
- Customize report access
- Email users
- Data Governance
- Adobe Analytics and GDPR
- Adobe Analytics and CCPA
- Frequently asked questions
- Adobe Analytics Data Privacy workflow
- View/manage report suite’s Data Governance settings
- Label report suite data
- Submit access and delete requests
- Data Privacy labels for Analytics variables
- Namespaces
- ID expansion
- Labeling best practices
- Labeling example
- Data Privacy and Data Connectors (Genesis)
- Data Privacy terminology
- Privacy Reporting Variables
- Server Call Usage
- Traffic Management
- Admin API
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 []
Because processing rules permanently affect Analytics data, Adobe strongly recommends that processing rules administrators receive certification training in Adobe Analytics, and be familiar with all sources of data for your report suites (standard web sites, mobile sites, mobile apps, Data Insertion API, and so on). Knowledge of the context data variables and standard variables populated in various platforms will help prevent accidental deletion or alteration of data.
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.
See Context Data Variables in Implementation Help.
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.
Using Context Data Variables in Reporting
Once context data variables are defined within your implementation, they must be copied to variables such as eVars to be used in reporting.
For more information, go here and here.