ECID regeneration on logout/login impacts push consent in Mobile SDK with Adobe Experience Platform
When Experience Cloud Identity (ECID) regeneration occurs during logout and login, consent enforcement breaks because the same device is treated as a new device. Using a stable person identifier resolves consent and push notification issues.
Description description
Environment
- Adobe Experience Platform (AEP)
- Mobile SDK
- Journey Optimizer
Issue/Symptoms
- Each logout and login cycle generates a new ECID when
resetIdentitiesis called. - The same device receives a new ECID and loses its previous consent history.
- Push notifications are sent to devices where users previously opted out of marketing communications.
- Consent enforcement breaks due to reliance on device-level ECID instead of a person-level identity.
Resolution resolution
Follow these steps to resolve this issue:
-
Do not rely on ECID as the primary identity for journey orchestration or audience qualification.
-
Use a stable person identifier, such as
CRM IDorPersonCustomerID, as the primary identity for all profile-level operations. -
Store and evaluate consent preferences against this stable person identifier instead of ECID.
-
In shared-device scenarios or environments with multiple logins on one device:
- Continue using
resetIdentitiesduring logout to prevent profile merging between different users. - After login, set the authenticated state for the stable person identifier (e.g., PersonCustomerID).
- Register push tokens only after authentication and associate them with the correct person identifier.
- Update consent preferences based on the authenticated user’s status.
- Continue using
-
For Journey Optimizer and message execution:
- Confirm that journeys and audience qualifications use the persistent person identifier instead of ECID.
- Avoid using ECID as an entry or qualification criterion for journeys or audiences that require long-term stability.
-
If further guidance is required for implementation strategy or schema design, contact the Adobe account team or a technical consultant for a tailored best practices review.
Verify
- After logging out and logging back in with different accounts on the same device, confirm that the correct consent status persists per individual user profile rather than per device or ECID.
- Verify that push notifications are sent only according to each user’s current marketing consent.
Additional information
- Adobe Experience Platform supports multiple ECIDs per profile, and there is no hard limit or penalty for accumulating multiple ECIDs when identity stitching rules are implemented correctly.
- Issues occur only when different individuals merge into one profile due to improper identity management.
- For compliance and predictable orchestration behavior, always prefer persistent person identifiers over device-based identifiers like ECID for consent enforcement and journey management.