Enable Identity Stitching in CJA Using ECID and Email — Migration from Adobe Analytics To CJA

Hi @mohitvashist 

I think you are on the right track, yes, identity stitching between ECID (anonymous web behavior) and email (authenticated identity) is absolutely achievable in AEP/CJA, without unnecessarily inflating your profile count in RTCDP.

1. Use Identity Graph in CJA & Not RTCDP

CJA supports identity stitching at reporting level, based on the identityMap in the Web SDK. You don't need to create full RTCDP profiles just to get stitched reporting in CJA.

• As long as both ECID and email are passed into the identityMap, CJA can stitch the journey once the same email appears in another dataset (like Marketo or CRM).
  
  

• So when a user submits a form, push email alongside ECID in the identityMap.
  
  
  identityMap: {
  ECID: [{ id: 'ecid-value-here', authenticatedState: 'ambiguous' }],
  email: [{ id: 'user@email.com', authenticatedState: 'authenticated' }]
  }
  
  

2. Disable Auto-Profiling in RTCDP for Anonymous ECIDs

To avoid burning B2B profile count on anonymous visitors -

• Configure Profile Merge Policies in RTCDP to only qualify profiles when an authenticated ID (like email) is present.

• Do not set ECID as a primary identity in your schema unless absolutely needed.

• Only ingest lead records into RTCDP once email (or another primary ID like CRM ID) is available from form fills or your Marketo/CRM feeds.
  
  

3. Once Marketo + Salesforce Are Connected

• Those systems will send known user data (like email, lead IDs, account details).

• AEP will use the identityMap to stitch the previously anonymous ECID behavior to the known user, enabling end-to-end journey reports in CJA.

Also, Please note that this stitching works in CJA even before RTCDP starts profiling the user, you don’t need to wait for full RTCDP integration.

Hope that helps!

Hi @mohitvashist ,

Below approach will ensure you get end-to-end journey visibility in CJA without burning your RTCDP profile budget.

1: Use Identity Stitching via Identity Graph in AEP

Ingest all your data (web, Marketo, SFDC) with proper identity mapping:

A. Web SDK (ECID)

• Use identityMap.ecid for all events

"identityMap": {
"ECID": [
{
"id": "your-ecid-value",
"authenticatedState": "ambiguous"
}
]
}

B. Form Submit with Email

On lead form submission, pass the email using identityMap.email

"identityMap": {
"email": [
{
"id": "john@example.com",
"authenticatedState": "authenticated",
"primary": true
}
]
}

This stitches ECID to email and qualifies it as a known identity in AEP, enabling identity resolution only when email is present.

2: Avoid Profile Count for Anonymous ECID

• You don’t ingest ECID-only data into Profile Store.
• OR you exclude ECID from identity namespaces that qualify profiles in RTCDP.

• Mark ECID events as profile-disabled during ingestion OR
• Do NOT enable Web SDK dataset for Profile, only enable the lead submission dataset (with email) for Profile.

3: Enable Identity Graph in CJA

When setting up your CJA Connection, make sure:

• You include both ECID and Email ID as identity namespaces.

• You enable Identity Graph Lookup:

  • This allows CJA to stitch behavior from ECID to email-based actions post-submission.

4: Bring in Marketo and SFDC (Later Phase)

When you ingest these:

• Use the same Email ID namespace used in Web SDK identityMap.

• Ensure both sources (Marketo, Salesforce) use the same identity.

• Once stitched, you'll see:

  • Pre-lead behavior (ECID)

  • Form submit (email)

  • CRM/marketing engagement (via joined email)

Thanks.

Pradnya