Understand how Elaine imports, stores, organizes, and activates contact and customer data.
Key concepts
- Contact profiles contain identifiers, master data, group data, permissions, and supported engagement information.
- Contact groups establish organizational or communication contexts; audiences select records using reusable conditions.
- Data sources describe acquisition context and can connect that context with PAC permissions.
- APIs support real-time operations, while SIEIS supports large and recurring file-based exchange.
How it works
- Define the system of record and stable matching keys for each data domain.
- Map incoming fields, formats, data sources, permissions, and group operations.
- Validate imports or API calls with a controlled sample.
- Activate approved data in audiences, personalization, and automations.
- Reconcile exports, errors, retention, withdrawals, and deletion across connected systems.
Governance and considerations
- Minimize duplicated ownership and prevent two systems from overwriting the same field without a rule.
- Keep persistent profile data separate from temporary transaction or event values.
- Monitor both technical transfer success and business-level record results.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.