> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squid-id.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify your install

> Use Test connection to confirm the Squid ID snippet is live and your site is sending traffic. Two checks: Deployed, then Connected.

After you [install the snippet](/getting-started/install-snippet), the install step shows a **Connection status** panel with a **Test connection** button. It runs two checks in order:

<Steps>
  <Step title="Deployed">
    Confirms the snippet is live on your page. Turns green with **Snippet is live** once we've seen the SDK actually run.
  </Step>

  <Step title="Connected">
    Confirms your site is sending live traffic. Turns green with **Your website is sending traffic**. When both checks pass, you'll see an **All set** badge.
  </Step>
</Steps>

## Run the test

<Steps>
  <Step title="Publish the snippet, then press Test connection">
    Make sure the snippet is added and your page is published. Then click **Test connection**.
  </Step>

  <Step title="Wait for Connected">
    We load your page once in the background so the SDK runs and connects. This can take **up to about 30 seconds** — the button stays on **Testing…** and can't be pressed again while it runs, so there's no need to keep clicking. **Deployed** shows its green check as soon as the snippet is confirmed; **Connected** follows once the live connection lands.
  </Step>
</Steps>

<Info>You don't have to keep the tab open. A real visitor loading a page also flips **Connected** on its own, at any time.</Info>

## "A different site's snippet is on the page"

If **Deployed** shows this warning, the snippet on your page belongs to a **different Squid ID website** (a snippet copied from another site, or an edited id). That other snippet loads a different site's SDK, so this website will never connect. Use **Copy this site's snippet** to grab the correct one, replace it, publish, and Test connection again.

## If we don't see the snippet

If the check can't find your snippet, you'll see: *"We don't see the Squid ID snippet yet."* Two things to try:

<Steps>
  <Step title="Confirm it's published">
    View source on a live page and check the snippet is in the `<head>` with your real SDK key (not the `YOUR_SDK_KEY` placeholder). With a tag manager or hosted platform, the change must be **published**, not just saved.
  </Step>

  <Step title="Open your website">
    Use the **Open your website** link to load your site in a new tab. A real page load runs the snippet — come back and the connection flips on its own. This is the reliable path for sites that build the page in the browser (Framer, Webflow, and similar), where a background check may not see the snippet.
  </Step>
</Steps>

## Continue without verifying

You can move past this step without a verified connection by choosing **Continue without verifying**. Until your snippet is live and verified, Squid ID can't identify your visitors or show any matches — so finish the install when you can. You can always come back and Test connection from **Settings → Websites → Install**.

<Warning>If the connection still won't confirm after the snippet is live and published, see [Troubleshooting](/troubleshooting) or contact [help@asksquid.ai](mailto:help@asksquid.ai).</Warning>

## Next steps

* [Identified visitors](/finding-visitors/identified-visitors): see who's showing up.
* [Route to Slack](/routing/route-to-slack): get matches without watching the dashboard.
