AI Dashboards - Traits Mapping

1. Overview

The Traits Mapping page is part of the AI Dashboards configuration system. It is used to define how raw event data fields are mapped into standardized “traits” for different event types (e.g., login, share, refund).

This ensures consistent data structure across events, making analytics and downstream processing easier and more reliable.

Left Sidebar (Configuration Menu):

Events Mapping → Main configuration screen (current view)
Search Query → Configure search-related mappings
Success Pages → Define success event/page tracking
Custom Mapping → Advanced or user-defined mappings

Top Right:

Website Selector (e.g., DEF) → Switch between environments or sites
Save Button → Saves all mapping changes

3. Events Mapping Structure

The configuration is written in a JSON-like format where each event type contains:

fields : key-value mapping of standardized traits → raw data fields

Example structure:

{
  "event_name": {
    "fields": {
      "trait_name": "source_field"
    }
  }
}

4. Event Configurations

The login event maps user authentication-related fields:

Trait	Source Field
cp1	customParameter1
cp2	customParameter2
cp3	customParameter3
cp4	customParameter4
cp5	customParameter5
email	data.e_mail
method	data.method
source	data.source
consent	data.consent
customerId	data.customer_id
customerType	data.customer_type

Purpose:

Standardizes login tracking data, including user identity, authentication method, and consent status.

The share event tracks content sharing actions:

Trait	Source Field
cp1	customParameter1
cp2	customParameter2
cp3	customParameter3
cp4	customParameter4
cp5	customParameter5
itemId	item_id
method	method
contentType	content_type

Purpose:

Captures what content was shared, how it was shared, and metadata about the content.

C. Refund Event Mapping (Partial)

The screenshot shows the beginning of a refund event configuration, but the full mapping is not visible.

Purpose (expected):

Likely used to standardize refund-related transaction data such as:

transaction identifiers
refund method
amount or status fields

5. Custom Parameter Fields (cp1–cp5)

These are flexible mapping slots:

Used to pass additional business-specific metadata
Mapped consistently across multiple events
Allow extensibility without changing core schema

6. Standard Field Types

Field	Description
email	User email address
method	Action method (e.g., login type, share method)
source	Origin of the event
consent	User consent status
customerId	Unique customer identifier
customerType	Type/category of customer
itemId	Identifier of shared content
contentType	Type of content being shared

7. Usage Flow

Select event type (login, share, refund, etc.)
Map incoming raw fields to standardized traits
Click Save to apply configuration
System uses mappings for event normalization and analytics processing

8. Purpose of Traits Mapping System

Ensures consistent analytics across different event sources
Reduces dependency on raw field naming differences
Enables scalable event tracking architecture
Supports multi-website or multi-environment configurations