Customer Data Platform (CDP) WebTag tracks visitor activities using first-party cookies. This page provides insights into the two methods used to implement the WebTag and explains how information is stored and used in the CDP system.
Understanding a cookie
Every time a user visits a website, a small text file is created and stored on their device to hold information about the visit. This text file is called a cookie, and it enables the server to recognize the user for authentication or tracking purposes.
Categories of cookies by function
There are two main types:
Authentication cookies that verify user identity
Tracking cookies that monitor user behavior across sessions
Categories of cookies by origin
There are two main types:
First-party are created by the website server during your first visit. They store information about sessions, viewed pages, items, and login details, helping the website optimize the overall user experience.
Third-party cookies are not created by the website server during your first visit. However, they do store information about sessions.
Note
CDP WebTag does not store customer visits within third-party sessions.
Workflow of first-party cookies in CDP systems
When a customer creates a profile on a site, the system records and stores the creation ID of the device as a first-party cookie. CDP implementations primarily rely on these first-party data captures and cookies saved by the site, as the platform uses embedded first-party cookies in the main domain. This process occurs while customers are logged in and identified during their site visits.
This approach ensures that the tracking aligns with the site's rules and the policies agreed upon by the customer when creating a profile and consenting to default site tracking policies. By following these guidelines ensures compliance with first-party cookie regulations.
The following table provides details of the cookie for CDP:
Name
Description
Duration
a1ashgd
This is the first-party cookie identifier.
1 year - auto extend
Consent Management Platform (CMP)
CDP WebTag works with any consent management system. Customer consent collection and management adhere to your governance and site policies. It is recommended to categorize the WebTag under first-party data policies, as this aligns with regulations like GDPR, CCPA, and other relevant state laws. This approach acknowledges and accepts your chosen level of data-sharing acceptance for personal information.
Mechanisms of CDP Cookies
Customer Data Platform (CDP) WebTag tracks visitor activities using first-party cookies. This page provides insights into the two methods used to implement the WebTag and explains how information is stored and used in the CDP system.
Understanding a cookie
Every time a user visits a website, a small text file is created and stored on their device to hold information about the visit. This text file is called a cookie, and it enables the server to recognize the user for authentication or tracking purposes.
Categories of cookies by function
There are two main types:
Authentication cookies that verify user identity
Tracking cookies that monitor user behavior across sessions
Categories of cookies by origin
There are two main types:
First-party are created by the website server during your first visit. They store information about sessions, viewed pages, items, and login details, helping the website optimize the overall user experience.
Third-party cookies are not created by the website server during your first visit. However, they do store information about sessions.
Note
CDP WebTag does not store customer visits within third-party sessions.
Workflow of first-party cookies in CDP systems
When a customer creates a profile on a site, the system records and stores the creation ID of the device as a first-party cookie. CDP implementations primarily rely on these first-party data captures and cookies saved by the site, as the platform uses embedded first-party cookies in the main domain. This process occurs while customers are logged in and identified during their site visits.
This approach ensures that the tracking aligns with the site's rules and the policies agreed upon by the customer when creating a profile and consenting to default site tracking policies. By following these guidelines ensures compliance with first-party cookie regulations.
The following table provides details of the cookie for CDP:
Name
Description
Duration
a1ashgd
This is the first-party cookie identifier.
1 year - auto extend
Consent Management Platform (CMP)
CDP WebTag works with any consent management system. Customer consent collection and management adhere to your governance and site policies. It is recommended to categorize the WebTag under first-party data policies, as this aligns with regulations like GDPR, CCPA, and other relevant state laws. This approach acknowledges and accepts your chosen level of data-sharing acceptance for personal information.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia CDP