Resolving profile count discrepancies in Adobe Experience Platform
In Adobe Experience Platform (AEP) Real-Time Customer Data Platform (CDP), the profile snapshot count often differs from the source system view. This happens because only qualifying profiles are included in the snapshot, while the source view shows all ingested profiles. This article explains the cause of the mismatch, its impact on license usage, and why the snapshot should be used for accurate reporting in B2B sandboxes.
Description description
Environment
Adobe Experience Platform (AEP) Real-Time Customer Data Platform (CDP)
Issue/Symptoms
- For example, the profile snapshot dataset shows around 24,000 profiles.
- However, the source System View shows over 100,000 profiles.
- Also, concerns whether the higher count affects license usage.
Note: For accurate license metrics, always use the daily profile snapshot dataset.
Resolution resolution
- The profile snapshot dataset only includes profiles that qualify for audiences and destinations. In this case, about 23,000 profiles are active and count toward license usage. The remaining profiles—around 80,000—exist in AEP but don’t qualify for any audience or destination, so they don’t impact licensing.
- In B2B sandboxes, AEP precomputes and joins B2B entities to improve preview query performance. This increases the total row count in sample data (from the
/previewsamplestatusAPI) compared to Business-to-Consumer (B2C) sandboxes. - Use the daily profile snapshot data to track license usage, as it accurately shows the number of addressable profiles.
- The UI shows data from the
core/ups/previewsamplestatusAPI, which includes precomputed results for faster performance. This doesn’t reflect actual addressable profiles and doesn’t affect license usage.
If you still see discrepancies or need help with merge policies or dataset setup, reach out to Adobe Support.