Skip to main content
bjoern-koth
bjoern-kothAccepted solution
Adobe Employee
July 2, 2025

Hi @saiteja_1225 

from where are you making the call? Your webserver or Launch server-side?

If you are using the HTTP API, different than using the Web SDK, this value will not automatically be added in your requests.

 

So, you must make sure to explicitly set the ECID value in either the identityMap (if available in your schema) or a dedicated ecid schema field that is flagged as identity.
In theory, this value should be present in the "kndctr_{YOUR-ORG-ID}_AdobeOrg_identity" cookie (Base64 encoded).

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/overview 

 

Alternatively, should you use the Web SDK, you can also get the ECID through an (async) call

await alloy("getIdentity").then(function(data) { console.log(">>> ECID is", data.identity.ECID); });

So, should you use Launch SSF, I would rather throw this in the XDM's data section to easily pick it up from there and use it in your HTTP API call. 

Cheers from Switzerland!
View in thread

3 replies

KumarRishii
KumarRishii
Level 5
July 2, 2025
You can refer to the following thread which addresses a similar query:
 
Translate
MohitVashist
Level 2
July 2, 2025

Addition to this you can also look into below options:- 

1. Verify the Schema Primary Identity: Confirm that the schema you are using for streaming ingestion has the correct field designated as the primary identity (e.g., ECID field).
Identity Map: Ensure that the identityMap is correctly configured and includes the ECID with the correct namespace (e.g., _adobe_corp.ecid).

2. Check the Incoming Data Valid ECID: Verify that the ECID value included in your streaming data is valid and matches the expected format for the ECID namespace.

Required Fields: If your schema requires other fields in addition to the ECID (e.g., email, phone number), make sure those fields are also present and populated with valid data.

Troubleshooting Steps
Inspect Batches: Use the Data Ingestion Service API to retrieve failed batches and inspect their details for more specific error information.

Documentation: https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/quality/retrieve-failed-batches

Note: Please check you have permission to fetch the API Request If not please refer the below documentation https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/postman

Translate
    bjoern-koth
    Adobe Employee
    bjoern-kothAdobe EmployeeAccepted solution
    Adobe Employee
    July 2, 2025

    Hi @saiteja_1225 

    from where are you making the call? Your webserver or Launch server-side?

    If you are using the HTTP API, different than using the Web SDK, this value will not automatically be added in your requests.

     

    So, you must make sure to explicitly set the ECID value in either the identityMap (if available in your schema) or a dedicated ecid schema field that is flagged as identity.
    In theory, this value should be present in the "kndctr_{YOUR-ORG-ID}_AdobeOrg_identity" cookie (Base64 encoded).

    https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/overview 

     

    Alternatively, should you use the Web SDK, you can also get the ECID through an (async) call

    await alloy("getIdentity").then(function(data) { console.log(">>> ECID is", data.identity.ECID); });

    So, should you use Launch SSF, I would rather throw this in the XDM's data section to easily pick it up from there and use it in your HTTP API call. 

    Translate
    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...