Customer Data Platform (CDP) implementations depend on first-party data capture. The process stores the device creation ID as a cookie on the site domain after a user creates a profile account. CDP depends exclusively on site-stored cookies. The platform integrates first-party cookies into the main domain to ensure that customer logins and identifications stay active throughout visits. The approach ensures compliance with site rules and policies, agreed upon when users create the profile and give consent to default tracking. Adherence to these rules ensures compliance with first-party cookie standards.
Capabilities
The following are the capabilities:
Customer profile accounts:
Websites collect data related to visitor profiles when users create accounts or log in. Cookies tie this data to the registered device ID as a first-party cookie. As data moves through the web traffic stages, sequential events activate based on customer interactions with pages.
Interaction tracking:
Default tracking captures various visitor interactions such as logins, page views, and add-to-cart actions. Event types define these interactions and map the active journey of visitors to align with the strategic goals of websites. The collection of detailed data, such as time spent on each page, provides insights into visitor behavior and preferences.
API mechanism integrations:
Script tags on the site initiate visitor requests back to the CDP tracker and transmits interaction events. Connection to the services endpoint assures the delivery of these data points to CDP.
Important considerations
The following are the important considerations:
- Data cannot be stored as third-party cookies because the cookie script is empty, which indicates that tracking does not occur for cookies outside your domain.
- The first-party cookie activates only when a visitor initiates site events such as logins, page views, or add-to-cart actions. The Software Development Kit (SDK) event listener initiates this activation.
- Anonymous visits remain untracked until visitor login identification recognizes the first-party cookie session.
Use cases
The following are the use cases:
- The domain stores device IDs of users who initially visit the website without linking them to profile accounts. After users register accounts, the website identifies their device IDs as cookies and enables CDP to capture various visitor interactions.
- The domain uses a first-party cookie to identify users who log in when they return to the website, and associate them with previous activities. This identification helps CDP to capture different types of visitor interactions.
- The domain does not activate the first-party cookie tracking for users who visit anonymously without logging in. CDP captures visitor interactions only after these users log in and are identified.
First-Party cookie vendor verification in CDP
Customer Data Platform (CDP) implementations depend on first-party data capture. The process stores the device creation ID as a cookie on the site domain after a user creates a profile account. CDP depends exclusively on site-stored cookies. The platform integrates first-party cookies into the main domain to ensure that customer logins and identifications stay active throughout visits. The approach ensures compliance with site rules and policies, agreed upon when users create the profile and give consent to default tracking. Adherence to these rules ensures compliance with first-party cookie standards.
Capabilities
The following are the capabilities:
Customer profile accounts:
Websites collect data related to visitor profiles when users create accounts or log in. Cookies tie this data to the registered device ID as a first-party cookie. As data moves through the web traffic stages, sequential events activate based on customer interactions with pages.
Interaction tracking:
Default tracking captures various visitor interactions such as logins, page views, and add-to-cart actions. Event types define these interactions and map the active journey of visitors to align with the strategic goals of websites. The collection of detailed data, such as time spent on each page, provides insights into visitor behavior and preferences.
API mechanism integrations:
Script tags on the site initiate visitor requests back to the CDP tracker and transmits interaction events. Connection to the services endpoint assures the delivery of these data points to CDP.
Important considerations
The following are the important considerations:
- Data cannot be stored as third-party cookies because the cookie script is empty, which indicates that tracking does not occur for cookies outside your domain.
- The first-party cookie activates only when a visitor initiates site events such as logins, page views, or add-to-cart actions. The Software Development Kit (SDK) event listener initiates this activation.
- Anonymous visits remain untracked until visitor login identification recognizes the first-party cookie session.
Use cases
The following are the use cases:
- The domain stores device IDs of users who initially visit the website without linking them to profile accounts. After users register accounts, the website identifies their device IDs as cookies and enables CDP to capture various visitor interactions.
- The domain uses a first-party cookie to identify users who log in when they return to the website, and associate them with previous activities. This identification helps CDP to capture different types of visitor interactions.
- The domain does not activate the first-party cookie tracking for users who visit anonymously without logging in. CDP captures visitor interactions only after these users log in and are identified.
Acquia CDP