querying the profile-store

1. Is profile-store data exposed in any dataset?

No, profile-store data is not directly exposed in any dataset.
Adobe Experience Platform’s data architecture consists of several components:

• Data Lake: Raw ingested data, accessible via Query Service and datasets.
• Identity Graph: For identity resolution, stores relationships, not directly queryable through Query Service.
• Profile Store: Holds the stitched, unified profiles; this is the “profile-store.”

While datasets in the data lake are profile-enabled (meaning they feed data into the Profile Store), the stitched, unified, current state view of a profile as maintained by the Profile Service (profile-store) is not itself exposed as a dataset in the data lake.

“Platform’s key data stores are the Identity Graph and Profile Store, which are separate from the data lake. … You can’t use [Query Service] to query identity graphs or profiles since those are accessed using other tools like segmentation and the Identity Service.”
— Query Service and Data Distiller overview

2. Can you query the profile-store using Query Service?

No, you cannot query the profile-store directly with Query Service.
Query Service is limited to running SQL queries on data in the Data Lake—specifically, datasets. All interactive and scheduled queries are run on tabular data ingested into the Data Lake, not on the Profile Store’s real-time, stitched records.

• Query Service can:

  • Query behavioral and attribute datasets (such as web events, CRM data) in Data Lake.
  • Query profile-enabled datasets (raw records before ingestion into profile-store).

• Query Service cannot:

  • Query the real-time, merged/stiched profiles as maintained in Profile Store.
  • Access profile-store aggregates used by Real-Time Customer Profile (RCP) or segmentation.

Source:

• Query Service and Data Distiller overview

• 3. Can you get the top 100 records from profile-store, except via the profile API?

  No, there is currently no means to get “top N” queries from profile-store using SQL or Query Service.

  • The Profile API (entities endpoint) allows you to fetch a specific profile by identity (e.g., email, ECID).
  • There is no public API or UI mechanism to fetch a list of profiles or perform an unbounded scan (“top 100”) on the profile-store.
  • Profile UI and Segmentation UI allow you to browse profiles or sample “profiles in segment”, but this does not provide arbitrary “top N” access to all profiles.

  Workarounds:

  • For any “top N records” from a population, you must query the data lake (datasets), not the profile store.
  • To preview a dataset (not profile store), the Query Service UI now uses a SELECT * LIMIT 100 query against the dataset in the data lake (not profile store). Read more: Dataset preview in Experience Platform.

  See relevant documentation:

  • Real-Time Customer Profile Troubleshooting Guide