I installed the snippet but see no data

One thing trips people up first: the collector replies 202 to every request — including the ones it drops. The reason for dropping is recorded on the project side and never sent back to the browser. A 202 in the network panel only proves the request left the browser, not that it reached your reports.

The only reliable check is the Real-time page in the console. The steps below work towards that.

1. Did the script load?

Open your site, press F12, switch to the Network panel, reload and filter for client.js.

• Request present, status 200 — the script loaded. Go to step 2.
• No request at all — the script tag isn't on the page. View the page source to confirm. Typical causes: the template change wasn't published, the tag went into a template only the home page uses, or a caching plugin is still serving the old page.
• Request failed or shown as blocked — usually an ad blocker or your site's Content Security Policy. See Content Security Policy and blockers.

2. Was the collection request sent?

Still in the Network panel, filter for pulse. After the page loads there should be one POST to api.pathclue.com.

If it's missing, the most common reason is that the browser has Do Not Track or Global Privacy Control switched on. With either signal the script doesn't run at all — deliberately, to respect the visitor's choice. Try a browser without those settings, or open the page on your phone over mobile data.

The other common reason: you are testing on localhost, which doesn't send by default.

3. Open Real-time

Once the request goes out, check Website analytics › Real-time for the last few minutes. If your visit is there, the other reports will catch up shortly. If it isn't, it won't appear anywhere else either.

4. Check the domain

Request sent but Real-time empty almost always means a domain mismatch. Look at the registered domains under Website analytics › Configuration › SDK code:

• Did someone enter https://example.com/ with the protocol and slash? Only example.com works.
• Are you browsing a different domain — say the registered one is production and you are on staging-example.net? Subdomains are allowed automatically; unrelated domains are not.

5. A few project settings

If the domain is fine, check these:

• Exclusion rules. Did you click "Exclude me" earlier, or add excluded paths? Exclusions run on the collector, so matching requests are never stored.
• Monthly quota. The Free plan includes 500,000 events a month. Beyond that, events aren't stored for the rest of the month; the counter resets on the 1st. Usage is under Plans & usage in the console.
• Time zone. "Today" follows the project time zone. If the project is several hours behind you, your visit may have landed in "yesterday".

Still stuck

Send us the site address, the exact page you opened, the time of the visit (to the minute) and a screenshot of the client.js and pulse requests in the Network panel. We can look up why the request was dropped. Chat or email both work.