CDP WebTag does not store customer visits within third-party sessions.
When a customer creates a profile (glossary term, activate to view definition) 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 |
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.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.