Learn how contact records, data fields, identifiers, and related information are represented in Elaine.
Key concepts
- The Elaine profile ID identifies a contact internally; external keys support reliable mapping to CRM or commerce records.
- Tenant-wide master fields describe common profile attributes, while group fields describe data specific to a contact-group membership.
- Persistent fields commonly use the configured c_ naming model; event and transaction fields can be handled separately.
- Membership, communication status, data source, PAC flags, and history provide context beyond ordinary attributes.
How it works
- Choose one or more stable external identifiers and define matching precedence.
- Classify every field by owner, purpose, type, allowed values, sensitivity, and retention.
- Create only fields needed by an approved activation or operational purpose.
- Map imports, APIs, forms, audiences, personalization, and exports to the same definitions.
Governance and considerations
- Email address alone is not always a durable business key.
- Changing field types or value ranges can invalidate content, filters, imports, or reports.
- Document null, empty, deleted, and unknown values explicitly.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.