This page provides insights into how Customer Data Platform (CDP) processes first-party cookie captures for the following scenario:
IT technicians aim to gain a comprehensive understanding of how CDP recognizes browsing activity and processes data to enhance the accuracy of customer profiles.
Verifying WebTag implementation using Google Chrome developer tools
To verify WebTag implementation, your IT team must complete the implementation process.
To ensure that the webtag is implemented correctly:
Open Google Chrome.
Navigate to your website.
From the main page, right-click anywhere on the page and select Inspect.
The page displays Google Chrome developer tools.
To verify the Acquia setup as a first-party cookie in the browser domain:
Click the Application tab in the developer tools.
In Cookies, select your website domain, such as https://www.acquia.com/.
In the search bar, enter the first-party cookie identifier, a1ashgd.
Verify that the cookie is present.
Cookie setup
Cookie name
Duration
a1ashgd
1 year - auto extend
As all components are available as expected, proceed with the stress test to identify potential blockers.
Verifying Acquia script for no cookie data
To confirm that the Acquia script remains empty and does not collect any cookie data:
Click the Application tab in the developer tools.
In Cookies, select your website domain, such as https://scripts.agilone.com.
Verify that it remains empty, as no cookies are collected or tracked.
If a cookie is present, take the following actions:
Contact your website team to verify the presence of the cookie.
Testing the impact of a third-party cookie blocker on WebTags
To determine the effects of third-party cookie blockers on your website's cookies and confirm their proper implementation:
Go to your Google Profile settings.
Search for third-party cookies.
Select Block third-party cookies.
Return to your website and reopen the Google developer tools.
Click the Application tab in the developer tools.
In Cookies, select your website domain, such as https://www.acquia.com/.
In the search bar, enter the first-party cookie identifier, a1ashgd.
Look for a "!" icon in the domain column to determine the effect of the blocker:
If no impact is observed, the third-party cookie block is not affecting your cookie, which indicates that it is correctly implemented.
If an impact is observed, the third-party cookie block is affecting the cookie.
Verifying CDP implementation for first-party cookie vendors
This page provides insights into how Customer Data Platform (CDP) processes first-party cookie captures for the following scenario:
IT technicians aim to gain a comprehensive understanding of how CDP recognizes browsing activity and processes data to enhance the accuracy of customer profiles.
Verifying WebTag implementation using Google Chrome developer tools
To verify WebTag implementation, your IT team must complete the implementation process.
To ensure that the webtag is implemented correctly:
Open Google Chrome.
Navigate to your website.
From the main page, right-click anywhere on the page and select Inspect.
The page displays Google Chrome developer tools.
To verify the Acquia setup as a first-party cookie in the browser domain:
Click the Application tab in the developer tools.
In Cookies, select your website domain, such as https://www.acquia.com/.
In the search bar, enter the first-party cookie identifier, a1ashgd.
Verify that the cookie is present.
Cookie setup
Cookie name
Duration
a1ashgd
1 year - auto extend
As all components are available as expected, proceed with the stress test to identify potential blockers.
Verifying Acquia script for no cookie data
To confirm that the Acquia script remains empty and does not collect any cookie data:
Click the Application tab in the developer tools.
In Cookies, select your website domain, such as https://scripts.agilone.com.
Verify that it remains empty, as no cookies are collected or tracked.
If a cookie is present, take the following actions:
Contact your website team to verify the presence of the cookie.
Acquia CDP