Questions to ask your third-party providers
This following step-by-step guide is helpful for site owners communicating with their third-party service providers about the use of third-party cookies (3PCs) on their websites. By following these steps, you can ensure your website continues to function smoothly with or without 3PCs.
Step 1: Pre-work
Before contacting your providers, it's essential to understand how third-party cookies are currently being used on your site. Audit your site or service to test for any potential breakages caused by the phasing out of third-party cookies.
Step 2: Contact your provider and ask these questions
Once you've identified the third-party cookies on your site, reach out to each provider through your designated point of contact or their support portal. Include information about the specific cookies they've left on your site and any observed impact on functionality when those cookies are blocked.
During your communication, ask your provider the following questions:
- Awareness of 3PC usage: "Are you aware of any third-party cookie usage with this product?"
- Limitations and solutions: "Are there any limitations to the product when third-party cookies are unavailable? If there are limitations, do you have any plans to resolve those?"
- Public readiness status: "Would you consider posting your readiness status on GitHub so other site owners know that you’re making plans?"
Step 3: Make any needed changes
Based on your provider's responses and plans, you may need to update tags or code on your site to ensure it functions correctly without relying on third-party cookies. This might involve:
- Implementing Privacy Sandbox solutions: If your provider chooses to use Privacy Sandbox solutions like FedCM, you may need to make adjustments. Reach out to your provider to understand if you need to take any action.
- Exploring alternative solutions: If your provider doesn't have a clear plan for operating without 3PCs, you may need to explore alternative solutions to ensure your website's continued functionality.
For more information about the changes to Chrome’s treatment of third-party cookies, refer to the developer documentation.