This page contains information for users who have already implemented the standard events tracking as defined in List of tracked events and Examples of web event tracking.
General information about CDP entities
Client-facing standard CDP entities:
These entities align with standard data feeds. Standard data feeds populate entities and their attributes. The entities and attributes configured for data feeds ingestion are available for the CDP Webtag to create or update. Objects in the CDP Webtag and related APIs respect the schema for standard data feeds. Always check with your CDP team because there are certain exceptions.
Providing entities and attributes in the feeds you send to CDP does not automatically mean that they are configured for webtag to use. You do not need to provide all entities and attributes through the feeds to use them in CDP. The CDP team can create some entities and attributes solely for webtag or API usage.
Important points
All entities have unique identifiers that must be provided to load the entity into CDP. Some entities offer multiple options for the identifier you can use. You must provide at least one identifier.
All data sources can send data about any entity in CDP. CDP consolidates the data to provide a consistent view on the entities that are loaded in the platform. This means that any data source can overwrite another data source’s data if they provide the same entity with the same identifier. The latest data source loaded into CDP overwrites previous data sources. CDP merges all the entities with the same identifier and selects the latest non-null value for each attribute.
CDP can accept different types of data and consolidate sparse data from multiple sources. You must send data from sources that you trust, and ensure you do not send overlapping data from other sources.