> AI agents: this is one page of nextanalytica's docs. The full index for agents: https://nextanalytica.app/llms.txt

# Troubleshooting

> Answers to the first problems people meet: no data, Verify, the wrong site in a source, the agent not connecting.

Updated: 2026-11-18

Something not working? These are the first problems people meet, each heading phrased the way people ask it. Find yours and follow the steps. Still wrong? Write to hello@nextanalytica.app.

## Why does my project say no data yet?

1. Open **Tracking**. If it says **Not on the site yet**, the tag isn't found: [add the tag](/docs/tracking/installation), deploy, then click **Verify**.
2. If it says live, open your site in a normal browser window. Visits appear within about a minute; ask your agent "Who's on the site right now?".
3. Visits are kept from the first verified visit on, never before it.
4. Your own browser may send **Do Not Track** or **Global Privacy Control**: those visits are never recorded. Your privacy settings work on you too, so check from another browser or your phone.

## Why does Verify say the tag isn't on the site?

The tag is on the site, but **Verify** disagrees. Check these:

- The line must carry this project's key. A line copied from another project counts for that project.
- The line must be on the page once, in the shared layout or through your Google Tag Manager tag. In the browser's developer tools, the Network tab shows a request to `t.nextanalytica.app`.
- A Content-Security-Policy may block the script: allow `https://t.nextanalytica.app` in `script-src` and `connect-src`. **Tracking** shows the exact change when it finds one.
- The site may be a different domain than the project's (`www` or another subdomain works; another domain needs adding in **Tracking**).

## Why does Search Console list other sites, not mine?

The Google account you signed in with can't see your site in Search Console. Either add your site in Search Console and click **Check again** in **Sources** > **Google Search Console**, or disconnect and sign in with the account that has it. [Google Search Console](/docs/sources/gsc).

## Why does my agent say it isn't connected?

1. Start a new session: a server added now shows its tools in a new session only.
2. In Claude Code, `claude mcp list` should say **Connected**. If it says it failed, run `/mcp` and sign in again.
3. If you revoked the key it used, the client can't offer the sign-in while the key is in its settings: it shows "rejected the configured Authorization header (HTTP 401)", or your agent has only a `reconnect` tool. Remove the server and add it again without the key: `claude mcp remove nextanalytica`, then `claude mcp add --scope user --transport http nextanalytica https://mcp.nextanalytica.app/mcp`, then `/mcp` to sign in. [Agent keys and OAuth](/docs/model-context-protocol/agent-keys#what-happens-when-i-revoke-a-key).

## Why does a source say "Couldn’t sync"?

The reason is under **Couldn’t sync** on the source's page. Most often the sign-in or key stopped working: connect it again on the same page, and the sync goes on. Each source's page lists its messages: [Sources](/docs/sources).

Canonical address: https://nextanalytica.app/docs/troubleshooting
