Why your data isn't showing up in Real-Time Customer Profile

Why this matters

This matters because if data doesn’t appear in the Real-Time Customer Profile, it can lead to incorrect customer insights, flawed targeting, and missed opportunities. Marketers and analysts rely on accurate, up-to-date profiles to make decisions—without them, actions like personalization or retargeting fail.

If a dataset isn’t enabled for Profile, or if its schema lacks a primary identity, records won’t be linked to any profile. Even if data is ingested, missing identity values mean no profile can form. Without a proper merge policy, fragments from different datasets won’t combine correctly, leaving gaps in the customer view. This chain of failures means data appears missing, even when it’s already in the system. Understanding these steps ensures you catch issues early and fix them before they impact decision-making.

The key ideas

Data only appears in Real-Time Customer Profile if the dataset is enabled for Profile. For a dataset to be enabled, its schema must also be enabled for Profile. A schema can only be enabled if it has a primary identity defined. Without a primary identity, the schema cannot connect records to a profile. Every record must have a value in the identity field—no value means the record won’t be linked to a profile.

The primary identity acts as the anchor that ties together data from different sources. Once records are linked, fragments from various datasets are combined into a single profile view using a merge policy. This policy determines how overlapping fields are handled when multiple datasets contribute to the same profile. The union schema combines all fields from Profile-enabled schemas that share the same class, forming a unified view of the customer.

To troubleshoot missing data, check in this order: first, ensure the schema is enabled for Profile; second, verify the schema has a primary identity; third, confirm each record has a valid identity value; finally, review the merge policy to understand how data is combined. This sequence covers the most common reasons data fails to appear in profiles.

How to apply it

Start by verifying that the dataset is enabled for Profile. If not, check its schema—data won’t appear in profiles unless the schema is enabled for Profile. Next, confirm the schema has a primary identity defined. Without a primary identity, the schema cannot be enabled, and no records will link to a profile. Then, examine each record in the dataset to ensure it contains a value in the identity field. If any record lacks an identity value, that record won’t be attached to a profile, even if the schema and dataset are correct. Once identity values are confirmed, review the merge policy to ensure it’s configured to combine fragments from the dataset into a single profile view. If the policy is missing or misconfigured, fragments may not merge properly, leading to missing data. Finally, check if the schema belongs to a union schema. If so, ensure all schemas in that union share the same class, so their fields are properly combined. Following this order—schema, dataset, identity values, merge policy—helps identify and resolve most cases where data fails to appear in Real-Time Customer Profile.

Mistakes to avoid

Avoid enabling a dataset for Profile without first checking that its schema is enabled for Profile. A schema must have a primary identity to be active, and without it, no records will attach to profiles. Also, ensure every record includes a value in the identity field—blank or missing values prevent profile linking.

Misunderstanding the merge policy can lead to data gaps. Even if all datasets are enabled and have valid identities, fragments may not combine as expected without proper merge rules. Always verify that the union schema includes all relevant fields from enabled schemas of the same class. Reviewing in order—schema, dataset, identity values, merge policy—helps catch these issues early and ensures data properly appears in real-time profiles.

Quick checklist

• Verify that the dataset is enabled for Profile.
• Confirm that the schema associated with the dataset is enabled for Profile.
• Ensure the schema has a defined primary identity.
• Check that every record contains a value in the identity field to link to a profile.
• Review the merge policy to confirm it combines fragments correctly from Profile-enabled datasets.
• Validate that the union schema includes all relevant fields from shared classes.
• Confirm identity values are present and consistent across records.
• If data is missing, trace the issue through schema → dataset → identity → merge policy.