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

# Verify installation

> Confirm the Traceten snippet is firing correctly on your site.

## What this lets you do

Confirm that the snippet is installed and sending events before you rely on the data.

## Using the dashboard verification panel

The fastest way to verify is through the dashboard.

<Steps>
  <Step title="Open your site in a new browser tab">
    Navigate to any page of the site where you installed the snippet. Let the page fully load.
  </Step>

  <Step title="Check the Verify step">
    In the [dashboard](https://app.traceten.com/dashboard), pick your site in the site switcher, open **Sites → Install** in the sidebar, and look at the **Verify** step.

    Within 30 seconds, you should see a green indicator confirming the snippet is live.
  </Step>
</Steps>

## Manual verification with browser DevTools

If the dashboard panel doesn't turn green, verify the snippet is present and firing using your browser's developer tools.

<Steps>
  <Step title="Open DevTools">
    On Chrome: right-click anywhere on the page and select **Inspect**, then click the **Network** tab.

    On Firefox: right-click → **Inspect Element** → **Network** tab.
  </Step>

  <Step title="Check that the script loaded">
    In the Network tab, filter by **JS** or search for `tt.min.js`. You should see a request to `cdn.traceten.com/tt.min.js` with a `200` status.

    If you don't see it, the `<script>` tag is not in the page's HTML. Go back and re-check your installation.
  </Step>

  <Step title="Check that events are being sent">
    In the Network tab, filter by **XHR** or **Fetch**, or search for `ingest.traceten.com`. After the page loads, you should see a POST request to `https://ingest.traceten.com/v1/events` with a `200` or `204` status.

    If you see the request but it returns a non-200 status, the event reached the server but was rejected. Check the response body for an error message.
  </Step>

  <Step title="Check the console for errors">
    In the DevTools **Console** tab, look for any errors referencing `traceten`. The snippet is designed to fail silently, so errors here are unusual. They can appear if the script tag is malformed.
  </Step>
</Steps>

## What a correct installation looks like

In your browser's Network tab, you'll see:

| Request                              | Status | Notes               |
| ------------------------------------ | ------ | ------------------- |
| `GET cdn.traceten.com/tt.min.js`     | 200    | Script loaded       |
| `POST ingest.traceten.com/v1/events` | 204    | Pageview event sent |

The POST body is a JSON payload containing your `data-site` key, page URL (with PII parameter values redacted), referrer, and anonymized behavioral signals. It does not contain your IP address. The IP is hashed at the edge before storage.

## Still not working?

Check the [troubleshooting guide](/install/troubleshooting) for the most common causes.