Does this change affect the entitlement packages I purchased?
No. You will still get the benefits of the entitlement packages that you previously purchased.
How come I see a different value for my Total Data Volume compared to my Profile store entitlement?
Total Data Volume represents the total amount of data available for Profile to use in engagement workflows. The measurement has been updated to be more deterministic and explainable. Most users should not see a significant change between their Total Data Volume and their total profile storage. If you have any concerns, please raise a ticket with your customer service representative.
How is Total Data Volume calculated? Does it include Data Lake storage?
Total Data Volume is calculated using the following formula:
Total Data Volume = Addressable Audience × Average Profile Richness
This metric reflects the total amount of data stored in the Profile Store that is available for Real-Time Customer Profile to use in engagement workflows. It does not include any data stored in the data lake.
Previously, some legacy offers used a “total storage” metric that combined both Profile Store and Data Lake usage. However, Total Data Volume is limited to Profile Store only, providing a more focused view of data relevant to profile-based engagement.
Do I need to recreate my changes to continue managing my Average Profile Richness?
No. Any actions, such as filtering, disabling profile for datasets, as well as setting up Experience event expirations and Pseudonymous Profile data expirations will continue to play a role in managing the Total Data Volume.
Why is the file I ingested into the sandbox a different size compared to the Total Data Volume?
Profile optimizes data for quick processing to execute the personalization and engagement workflows that the system is designed for. The file size on the client-side may be different from the Total Data Volume because of factors including the type of encoding, compression, and format.
Does this change apply to SKUs that have a shared limit for both Profile and data lake?
Customers that are on SKUs that have shared Average Profile Richness between Profile and data lake will continue to see the Total Consumed Storage metric, and will not see the Average Profile Richness metric.