Most common mistakes when using Adobe Experience Platform Identity Service
Missing ECID on Page Load
Challenge: The ECID is not generated or retrieved properly during page load.
Impact: Adobe cannot link sessions to a user profile.
Inconsistent ID Types Across Channels
Challenge: Different ID types are used across app and web platforms.
Impact: Prevents accurate cross-channel user matching.
Unlinked Customer IDs
Challenge: CRM or email-based IDs are collected but not sent to AEP for linkage.
Impact: Limits the ability to build complete customer profiles.
Improper Hashing or Format Errors
Challenge: IDs are not hashed correctly (e.g., missing SHA-256) or use the wrong format.
Impact: Causes ingestion failures or profile mismatches.
Lack of Consent Management Integration
Challenge: Privacy restrictions block data collection, but no alerts are triggered.
Impact: Silent data loss and compliance blind spots.
How Trackingplan solves your problems with Adobe Experience Platform Identity Service
Trackingplan monitors every request to the Identity Service so you can be confident that profiles across devices and systems remain accurately linked and privacy-compliant.
Identity Presence Checks
Ensures ECID, customer IDs, and declared IDs are all collected and sent with each event.
Format and Hash Validation
Verifies ID formats and alerts when values are missing, malformed, or unlinked.
Cross-Device Identifier Mapping
Helps identify gaps in identifier consistency across platforms and sessions.
Privacy Signal Awareness
Highlights when identifiers are dropped due to consent-related settings.
Frequently asked questions about Adobe Experience Platform Identity Service
How can I confirm that ECIDs are being sent on all events?
Trackingplan inspects every hit and confirms that essential identity fields—like ECIDs, custom IDs, or hashed emails—are consistently attached. This ensures that your user profiles in AEP are populated correctly and data is attributed properly across sessions and platforms.
Why aren’t profiles being unified in AEP?
Inconsistent or missing identity fields are the #1 reason user profiles fail to unify in AEP. Trackingplan detects these gaps, flags where the breakdowns happen, and helps your team troubleshoot why user data isn’t stitching together—before it results in reporting gaps or targeting issues.