Adobe Commerce Data Connection – What type of Identity Namespace should I set as Primary Identity?

[Siva001]

Hi Community,

I am trying to integrate Adobe Commerce with Adobe Experience Platform (AEP) using the Data Connection extension.

• I have created an event schema and a profile schema.

• I noticed that I cannot choose ECID (it seems to be default and not selectable).

• Now I want to know what type of Identity Namespace I should set as the Primary Identity for both schemas.

Should I use Email, ECID, or some other namespace?
What is the best practice for Adobe Commerce → AEP integration?

[Devyendar]

Adobe Commerce connector allows you to capture 3 types of data in AEP.

1) Storefront (client-side via Datastream → Experience Events)

• Web SDK sends ECID by default for anonymous traffic.
• On login/identify, also send a durable person ID in identityMap (prefer Commerce Customer ID in a custom namespace; fallback Email/Email_LC_SHA256).
• Use ECID for device continuity; don’t use ECID as the profile’s primary ID.

2) Back Office (server-side events)

• Connector sends events with identityMap that includes email when available and ECID.
• For strongest stitching, also include Commerce Customer ID using the same custom namespace you use on the storefront.

3) Profile (customer attributes → Profile dataset)

• Send shopper profile attributes on a Profile schema/dataset.
• Set primary identity = Commerce Customer ID (custom namespace); if unavailable, use Email_LC_SHA256.
• Keep the same person-ID namespace across Storefront + Back Office + Profile so profiles stitch cleanly.

Refer to the detailed documentation here https://experienceleague.adobe.com/en/docs/commerce/data-connection/fundamentals/connect-data#send-c...