Real-Time CDP · licence usage
How much of the licence is used
An online shop with 800,000 registered customers buys Real-Time CDP for 2 million profiles. It looks like plenty. But every anonymous visitor to the website is also a profile, and every event that enters the profile takes up space.
Example assumptions
Example shop, traffic and sizes. Real sizes depend on how Profile optimises the data, not on the size of the ingested files. The 75 KB per profile applies to the Real-Time CDP B2C edition.
Addressable Audience
Profiles against the licensed amount
Profiles in the Profile store, known and pseudonymous, month by month. Licensed: 2,000,000.
Total Data Volume
Data against the allowed amount
Data in the Profile store; the data lake does not count here. Allowed: 150 GB, 75 KB per licensed profile.
Reading
What makes each figure grow
Pseudonymous profiles inflate the audience. Events inflate the volume. Each expiry acts on one of the two.
The recommendation
Only what gets activated goes into the profile, with an expiry date
The Profile store is for acting in real time, not for keeping everything. What is useful for analysis can stay in the data lake, which does not count towards Total Data Volume.
- 01
Pseudonymous profile data expiry
Profiles with only an ECID that do not come back are deleted from the Profile store once the period ends. The period depends on how long an anonymous profile is useful for remarketing or personalisation.
- 02
Filter before ingestion
Exclude fields and events in the Web SDK, the Mobile SDK or the Analytics source connector. Enable for Profile only the datasets used in audiences or personalisation.
- 03
Experience Event expiry per dataset
Behavioural events leave the profile once they are no longer useful. It does not delete attributes or profiles, so on its own it is not enough.
- 04
Check the usage dashboard every month
The licence usage dashboard shows Addressable Audience and Total Data Volume per sandbox. The identity graph does not count as profiles.