Guidance on Adding ECID to the Experience Event Schema | Community
Skip to main content
A
AEPuser16
Level 2
October 27, 2025
Solved

Guidance on Adding ECID to the Experience Event Schema

  • October 27, 2025
  • 2 replies
  • 219 views

Hi,

 

If we receive ECID as one of the fields from the source data (CSV file from the cloud storage source), what is the best approach to include this ECID in the existing Experience Event schema?

Should we add it as a string field in one of our existing custom field groups, since there is no option to include it under the identityMap?

Note: We already have a primary identity (e.g., CRMID) in the Experience Event schema, and this schema is not enabled for Profile, as we are using it only in CJA and not in RTCDP. Therefore, we would like to add ECID and use it as a secondary identity to enhance graph-stitching capabilities.

Please suggest the best way to add ECID in this scenario.

 

Thanks!

Best answer by Karuppiah_Sakthivel

Hi,

Since your Experience Event schema is not Profile-enabled (used only in CJA), the best approach is to add the ECID as a simple string field in one of your existing custom field groups — not under identityMap.

The identityMap object is only leveraged when a dataset is enabled for Real-Time Customer Profile. In your case, since Profile stitching does not apply, adding ECID there won’t have any functional effect.

Recommended approach:

  • Create or use an existing custom field group (for example, _customIdentifiers).
  • Add a new field, e.g. _customIdentifiers.ecid (type: string).
  • Map your ECID value from the source file to this field during ingestion.

This way, ECID will be available for use in CJA reporting or correlation, and if you decide later to enable the dataset for Profile, you can simply mark this field as an identity (with namespace = ECID).

2 replies

K
Karuppiah_SakthivelAccepted solution
Level 4
October 27, 2025

Hi,

Since your Experience Event schema is not Profile-enabled (used only in CJA), the best approach is to add the ECID as a simple string field in one of your existing custom field groups — not under identityMap.

The identityMap object is only leveraged when a dataset is enabled for Real-Time Customer Profile. In your case, since Profile stitching does not apply, adding ECID there won’t have any functional effect.

Recommended approach:

  • Create or use an existing custom field group (for example, _customIdentifiers).
  • Add a new field, e.g. _customIdentifiers.ecid (type: string).
  • Map your ECID value from the source file to this field during ingestion.

This way, ECID will be available for use in CJA reporting or correlation, and if you decide later to enable the dataset for Profile, you can simply mark this field as an identity (with namespace = ECID).

    itsMeTechy
    itsMeTechy
    Level 4
    November 3, 2025

    Hi @aepuser16 

     

    It is possible to ingest into identityMap, even when you ingest data from csv file. you need to use the data prep (sample given below) and form the identityMap and you can ingest into it in the target dataset. As you want to use Graph Based stitching capability, this schema/dataset must be enabled for profile. 

     

    toObject(
    "ECID", toArray(toObject("id", <ecid attribute>, "primary", true)),
    "CRMID", toArray(toObject("id", <crmid attribute>))
    )

     

    you have even change this to consider CRMID as primary true as per your requirement.

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...