Real-Time API Ingestion – Handling Partial Composite Identities in AEP

We’re implementing AEP for real-time API-based data flows. Our identity model uses a composite key, for example:
compositeId = field1 + field2

The primary real-time source only provides field1, while field2 exists in another source system that is ingested separately. Because AEP relies on the complete composite identity for stitching and unified profile creation, this leads to incomplete or fragmented profiles.

We’re exploring the best architectural approach within AEP to handle scenarios where only part of a composite identity is available in real time.