Profile Concepts and Components
Understanding Profiles
A profile serves as the foundational data model in Detect. It represents a specific entity type (such as Customer, User, or Subscriber) and defines the attributes available for audience segmentation and personalization in pipelines.
Profile Attributes
Attributes are individual data fields within a profile that represent customer or audience member characteristics. Attributes are mapped from database columns and can include information such as:
- Identifiers (AUDIENCE_KEY, CustomerID)
- Demographics (firstName, lastName, age, gender)
- Contact Information (email, phone, address)
- Temporal Data (Date of Birth, registration date)
- Other categorical or numerical data
Attribute Mapping
Attribute Mapping is the process of connecting database columns to profile attributes. During mapping, you specify:
- DB Column Name (Type)
- The source database column name and its data type (String, Int64, DateTime, etc.)
- Attribute Name
- The business name for the attribute in the profile
- Key Attribute
- A boolean indicator specifying whether this attribute uniquely identifies records
Key Attribute
Every profile must have exactly one Key Attribute. The key attribute serves as the unique identifier for each record in the profile. This attribute is used to:
- Match incoming feed data to profile records
- Track audience members across pipelines
- Link transactional and enrichment data to the profile
The key attribute for every profile must correspond to the primary key of its associated database table. The primary key uniquely identifies each record in the table.
Profile Status
Profiles can exist in the following states:
- Draft: Profile is being created or edited but not yet active
- Active: Profile is ready and can be used in pipelines
- Master Profile: The primary profile in the system; at least one master profile must exist