This article describes the prefixes you must attach to key variables when creating trait rules.
When you create Trait Builder rules, it is important to preface the key variable with a recommended prefix. These prefixes identify the type of data passed in and help avoid namespace conflicts within Audience Manager. Generally, you can give a variable any name, but data for a rule will not process if the key variable name does not match the variable name in an event call.
The following table defines the common prefixes used by Trait Builder.
|Key variable prefix
|Identifies the variable
As customer specific. This is key data sent in from your own properties.
At the Audience Manager level. This data is uniform across the Audience Manager ecosystem. See Supported Attributes for DCS API Calls for a more complete list.
That contains HTTP header information. Includes header parameters such as
Note: For customers using DIL versions older than 9.0, data collection using the
Signals using this prefix are not surfaced in Signal Search.
Our Data Collection Servers allow passing of private parameters. Basically, any parameter that starts with