Chrome is starting to deprecate third-party cookies as of January 2024. The deprecation process will start with a 1% test in the first quarter of 2024, with plans to fully deprecate third-party cookies by the end of 2024. Because of Looker's dependency on third-party cookies to establish embed user sessions, this may impact your embed use case. Any embed customer that has not set up a custom domain for their Looker instances and is not using cookieless embedding will need to take action.
Implement one of the following solutions to ensure that your embed use case continues to work for all your embed users:
Set up a custom domain for your Looker instance.
You can set up a custom domain for your Looker instance that shares the same domain as your embed application. Configuring a custom domain causes the cookies that Looker uses to become first-party cookies, since the Looker domain matches the embed application domain. For example, if you are embedding on
analytics.mycompany.com, you can set up a custom domain that changes your Looker URL frommycompany.cloud.looker.comtolooker.mycompany.com.To set up a custom domain on a Looker (original) instance, contact Looker Support.
To set up a custom domain on a Looker (Google Cloud core) instance, follow the instructions in the Set up a custom domain for a Looker (Google Cloud core) instance documentation page.
Switch to using cookieless embedding.
Cookieless embedding uses a token-based approach for embed user authentication that bypasses Looker's dependency on browser cookies. This functionality is generally available, but requires embed application code changes to implement. For more information, see the Cookieless embedding documentation page.
If you have any questions or need assistance, contact Looker Support.