This document describes how to troubleshoot issues with setting up Looker embedding. If your embedded content fails to load, there are several possible reasons to check.

## Decision tree

Use the following decision tree to troubleshoot embed setup issues:
<iframe src="https:///frame/looker/docs/best-practices/flows/troubleshooting-embed-setup_bbd707258507ed081c84e5f56e7fc8f89ff81a667c207e9907398f0680f33e87.frame" class="framebox inherit-locale " allow="clipboard-write https://" allowfullscreen is-upgraded></iframe>

## Troubleshooting steps

The following sections describe the scenarios in the tree in further detail.

### Is this signed embedding?

See the [Signed embedding](https://docs.cloud.google.com/looker/docs/signed-embedding.md.txt) documentation for more information about signed embedding.

If you're using signed embedding, proceed to [Does private embed work?](https://docs.cloud.google.com/looker/docs/best-practices/flows/troubleshooting-embed-setup.md.txt#private_embed_works). If you aren't using signed embedding, see [Third-party cookie issue](https://docs.cloud.google.com/looker/docs/best-practices/flows/troubleshooting-embed-setup.md.txt#third_party_cookie).

### Does private embedding work?

Check whether [private embedding](https://docs.cloud.google.com/looker/docs/private-embedding.md.txt) works.

If private embedding works, proceed to [Signed embedding troubleshooting](https://docs.cloud.google.com/looker/docs/best-practices/flows/troubleshooting-embed-setup.md.txt#signed_embed_troubleshooting). If private embedding doesn't work, see [Third-party cookie issue](https://docs.cloud.google.com/looker/docs/best-practices/flows/troubleshooting-embed-setup.md.txt#third_party_cookie).

### Third-party cookie issue

Check the domain of the embedded platform and the domain of the embed URL. If the base domains don't match, the issue may be caused by third-party cookies being blocked by the browser.

For example, if your embed application is hosted on `example.com` but your Looker instance URL used for embedding is `customer.cloud.looker.com`, browsers may block cookies from `customer.cloud.looker.com` when the Looker iframe is embedded in `example.com`. If your Looker instance was instead on `looker.example.com`, cookies would be first-party as base domain `example.com` matches.

If the issue is caused by third-party cookie denial, you can either enable third-party cookies in your browser or configure a custom domain. For Looker (Google Cloud core) instances, you can configure a [custom domain](https://docs.cloud.google.com/looker/docs/looker-core-custom-domain.md.txt) using self-service. For Looker (original) instances, a [custom domain](https://docs.cloud.google.com/looker/docs/best-practices/how-to-change-the-looker-instance-url.md.txt) can be configured by request to align your instance domain with the embedding application's base domain.

### Troubleshooting signed embedding

If you're experiencing issues with signed embedding, see the following troubleshooting pages:

- If you don't see the Looker UI or see only the login page, consult [Troubleshooting signed embed authentication errors](https://docs.cloud.google.com/looker/docs/best-practices/how-to-troubleshoot-signed-embed-authentication-errors.md.txt).
- If you see the Looker UI but are encountering 404s, permissions, or content access issues, consult [Troubleshooting signed embed 404s, permissions, and content access](https://docs.cloud.google.com/looker/docs/best-practices/how-to-troubleshoot-signed-embed-404s-permissions-content-access.md.txt).

## Final review and support

If the embedded iframe is still failing to load, review the troubleshooting steps on this page. If you still need help, gather the following information before you [contact Support](https://docs.cloud.google.com/looker/docs/best-practices/looker-support-details.md.txt):

- A [HAR file](https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting) from a network capture taken while reproducing the embed issue
- The type of embedding being used: [Public](https://docs.cloud.google.com/looker/docs/publishing-looks-with-public-urls.md.txt), [Private](https://docs.cloud.google.com/looker/docs/private-embedding.md.txt), or [Signed](https://docs.cloud.google.com/looker/docs/signed-embedding.md.txt)
- When the issue started occurring