Parameters Management

With this release, Oracle has introduced the Parameters management area which enables you to define and manage parameters used to capture event data. Parameters are key-value pairs that make up a web event, most commonly, collected by a tracking tag as visitors or users engage with web properties and other marketing content, for example. Once configured, a parameter can be used to define behavior signals of interest and attributes associated to a behavior.  

Business Benefits:

• Parameters can be used to define behavioral signals of interest that trigger subsequent marketing actions

• Parameters are foundational for defining behavior attributes used in trigger rules, segments, and personalization of content

• Many commonly used parameters are pre-configured and ready to use

Steps to enable and configure

You don't need to do anything to enable this feature.

Tips and considerations

How to Start Using

• Navigate to Parameters under Data Streams. 
• Use the Parameters list page to search, view, or create parameters. 
• Click Create to define a new parameter or select from Discovered Parameters (auto-detected from incoming data)
• Define required fields:
  • Parameter Key (unique identifier used in event payloads)
  • Display Name (user-friendly label)
  • Category (logical grouping such as Events, Campaigns, Device, Geo, etc.)
• Optionally apply transformations to standardize incoming values
• Use parameters in:
  • Behavior Expressions (e.g., event logic such as “Action Type = click”)
  • Event Attributes (as the source for profile and event-level attributes)

Tips and Considerations

• Parameters can be pre-defined or custom-created—prefer reuse before creating new ones
• Always define clear and consistent naming conventions for parameter keys and display names
• Parameter keys are critical for data collection and must be unique
• Use categories to logically organize parameters and improve usability across teams
• Leverage transformations (e.g., change case, trim whitespace, find/replace) to standardize data before use
• Transformation order matters and is applied sequentially across all usages of the parameter
• Changes to parameters or transformations impact all dependent behaviors and attributes globally
• Regularly review unused or redundant parameters to maintain data hygiene
• Use discovered parameters to avoid duplication and align with actual incoming data streams