--- title: "Verifying CDP implementation for first-party cookie vendors" date: "2025-03-22T13:29:53+00:00" summary: "Learn how to verify CDP implementation for first-party cookies, ensuring accurate customer profiles and optimal data processing." image: type: "page" url: "/customer-data-platform/verifying-cdp-implementation-first-party-cookie-vendors" id: "c87380a8-c419-445f-8128-0208535bb901" --- 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: 1. Open Google Chrome. 2. Navigate to your website. 3. From the main page, right-click anywhere on the page and select **Inspect**. The page displays Google Chrome developer tools. ![Context menu with options like Exit Full Screen, Reload, Save As, Print, Translate to English, and Inspect. Includes AdBlock and Toby extensions.](https://acquia.widen.net/content/3cf998b2-8eeb-478d-bf9c-5ede79277b8e/web/cdp_google-dev-tool-inspect.png) 4. To verify the Acquia setup as a first-party cookie in the browser domain: 1. Click the **Application** tab in the developer tools. 2. In **Cookies**, select your website domain, such as `https://www.acquia.com/`. ![Developer tools interface showing application tab with storage options like cookies, local storage, and IndexedDB highlighted.](https://acquia.widen.net/content/8bc42151-8d04-4ff5-913e-ed8d5f152069/web/cdp_application-cookies.png) ![Web browser cookie list showing URLs for acquia.com and app.qualified.com.](https://acquia.widen.net/content/4a7763db-322c-4c84-8398-ee708abbc2d5/web/cdp_app-cookies.png.png) 3. In the search bar, enter the first-party cookie identifier, `a1ashgd`. ![Browser developer tools showing a cookie named "statpop" from acme.com, with a specific value, size, and expiration date.](https://acquia.widen.net/content/4316965d-6c63-4a9d-aa8e-fa86b22241dd/web/cdp_first-party-cookie-identifier.png) 4. 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: 1. Click the **Application** tab in the developer tools. 2. In **Cookies**, select your website domain, such as `https://scripts.agilone.com`. ![A dark-themed file management interface showing local and cloud storage options on the left, with a blank file list on the right.](https://acquia.widen.net/content/38dc1c01-6f6a-4c76-9046-67fbc93673d8/web/cdp_cookie-scripts.png) 3. Verify that it remains empty, as no cookies are collected or tracked. 4. If a cookie is present, take the following actions: 1. Contact your website team to verify the presence of the cookie. 2. Open a [Support](https://insight.acquia.com/support) ticket for further investigation. 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: 1. Go to your **Google Profile** settings. ![Browser menu screenshot showing options for new tabs, history, downloads, settings, and more, with a signed-in profile and zoom controls.](https://acquia.widen.net/content/5bf7ad36-8b54-4462-9281-ec63fc23f1d1/web/cdp_google-profile-setting.png?h=709&itok=c_8NuB_Y) 2. Search for third-party cookies. ![Search results for "Third-party Cookies" in browser settings, highlighting privacy and security options.](https://acquia.widen.net/content/10ca2e7b-d5a8-4443-892c-5e00f0aeca43/web/cdp_third-party-cookies.png?w=717&itok=G6fa5Mok) 3. Select **Block third-party cookies.** ![Browser settings screen showing options to manage third-party cookies with colorful geometric shapes in the background.](https://acquia.widen.net/content/796033fd-ce58-4f75-bce7-1f721b62ea85/web/cdp_block-third-party-cookies.png?w=705&itok=mmgTaftX) 4. Return to your website and reopen the Google developer tools. 5. Click the **Application** tab in the developer tools. 6. In **Cookies**, select your website domain, such as `https://www.acquia.com/`. 7. In the search bar, enter the first-party cookie identifier, `a1ashgd`. 8. 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. ![Browser console showing a cookie with name, value, domain, and expiration date details. Cookie size is 39 bytes, with medium priority.](https://acquia.widen.net/content/f0778073-e32c-4e3b-94d1-5b6682987aba/web/cdp_website-domain.png) * If an impact is observed, the third-party cookie block is affecting the cookie. ![Blocked cookie message detailing domain mismatch and expiration date of May 8, 2025, in a browser console.](https://acquia.widen.net/content/1437ccb2-ed0d-40e2-bbbd-f841b4b0d5d8/web/cdp_domain.png) 9. Toggle the third-party cookie blocker on and off at the beginning or end of the browser session for further testing. ![Browser pop-up showing cookie settings for acquia.com, including third-party cookies blocked and four sites allowed. Options to manage cookies and settings.](https://acquia.widen.net/content/3391fd10-82e1-4bf1-b15a-81b1e723ac25/web/cdp_cookie-site-data.png?h=421&itok=VULX5JnC) ![Website homepage with "Build a Better Digital Experience" text. Notification about blocking third-party cookies is displayed on the right.](https://acquia.widen.net/content/9cee31ae-16e1-42dc-9678-a0ca76f2a6a2/web/cdp_incognito-mode.png?w=720&itok=Kd2wgbUE) 10. Repeat the same test in **Incognito** mode by changing the Google setting to **Block Third-party Cookies in Incognito mode** to determine any difference.