ComposableStack.AI CDP
Back to agent
Operational Taskoperational-task.inspect-unified-customer-profile

Inspect and validate a unified customer profile via UI, API, and diagnostic tools

Verify that behavioral events, profile attributes, and segment memberships are correctly unified and accessible through the platform UI, a REST API client, and a browser-based event debugger.

confidence 85%v2reviewed May 17, 2026profile-inspection, validation, profile-api, debugger, xdm, unified-profile, identity-namespaces, troubleshooting

Inspect and validate a unified customer profile via UI, API, and diagnostic tools

Profile inspection is the practitioner's primary validation loop: it confirms that the collection and ingestion pipeline is working correctly, that identity stitching has fired, and that segment membership is accurate. It is also the surface used by call-center agents and operations teams to look up customer context in real time.

Multiple access surfaces serve different audiences. The platform UI serves analysts and operations staff who need to answer ad-hoc questions without writing code. The REST API serves application developers who need to embed profile lookups in operational tooling (call center apps, real-time personalization engines). Browser-based debuggers serve implementation engineers who need to verify that the Web SDK is emitting the correct XDM payload before events reach the data store.

What to check. A correctly unified profile shows: (1) all expected identity namespaces linked (ECID, email, phone), (2) pre-registration anonymous events merged to the authenticated profile, (3) cross-channel events from both web and mobile appearing in the unified event timeline, (4) segment membership populated based on behavioral criteria.

Identity namespace lookups. Every platform that exposes a Profile API allows lookup by a namespace + value pair. In AEP the namespaces are configured (Email, ECID, Phone, CRMID, etc.); in CDW-native stacks the equivalent is a join key on the identity resolution output table. The lookup surface differs; the data structure question ("which identifier do I use to find this customer?") is universal.

Parallel viability (high). CDW-native stacks expose profile data via SQL queries on the CDW (Snowflake Worksheet, BigQuery Console), a dbt-compiled profile model, or a reverse-ETL tool's audience preview. AEP's Profile UI has no direct CDW equivalent, but the underlying data is equally inspectable via SQL. Phase 3 will document Snowflake SQL inspection; Phase 4 will cover Hightouch Customer Studio profile lookup.

Sources