Analytics for builders
Why your first page view is not showing up, ranked by likelihood
By Jonas Reed · Nov 1, 2026 · 9 min read
You added the script, opened your site, and the dashboard says nothing happened. Before you reinstall anything, spend ten minutes on the checks below. They are ordered by how often we expect each one to be the cause, cheapest check first.
One limit up front. The ordering is our judgment, built from the failure lists in vendor documentation and from the way installs go wrong with an AI coding agent. It is not a measured frequency, and we know of no published table that ranks these causes by how often they occur. If your case breaks the order, trust the evidence on your screen over the list.
Where you are probably testing
The most likely place your own visit disappears is your own browser. Statcounter's worldwide figures for September 2026 put Chrome at 66.36% of browser use, with Safari at 18.27% and Edge at 6.04%. Statcounter counts browsers, not blocking, so the chart does not say how many of those browsers run a blocker. It tells you which profile you are most likely testing in: a Chrome profile you have used for years, with extensions you forgot you installed.
Source: Statcounter Global Stats, Browser Market Share Worldwide - September 2026, Sep 2026. Retrieved Oct 29, 2026.
1. The tag is not on the live page
Start here because it is the cheapest to rule out and the most common with a deploy pipeline in the middle. You edited a layout file, the build did not run, or a cache served the old HTML. Plausible's troubleshooting guide lists this directly: cached pages can serve an old version without the snippet, so you purge the cache after adding or changing it.
Ask the live site, not your editor:
curl -s "https://yoursite.com/?nocache=$(date +%s)" | grep -o '<script[^>]*usepeeko[^>]*>'
Replace yoursite.com with your domain. You should see one line that contains usepeeko.com/t.js and your site key. If the command prints nothing, the tag is not in the HTML your server returns. Check that the commit deployed, that the tag sits in the <head> of the layout every page uses, and that a CDN or framework cache is not holding the old page. If the tag appears only after a client-side render, view the page in a browser instead, since curl shows only the HTML the server sends.
The install snippet is a single tag:
<script defer src="https://usepeeko.com/t.js" data-site="YOUR_SITE_KEY"></script>
If you used a builder prompt, our post on adding analytics to Lovable, v0 and Bolt with one prompt covers where each of them puts the tag.
2. You tested on localhost or a preview URL
Some trackers switch themselves off on localhost. Plausible's documentation says its script "automatically disables itself on localhost." Whether yours does depends on the tool, so read its docs before you assume.
The second version of this problem is one you cause on purpose. If you gated the tracker by hostname so that only your real domain records visits, then a preview deploy, a staging URL or a local production build records nothing, by design. That setup is the right one, and we describe it in keeping your own visits out of site analytics. It does mean your first test has to be on the live domain.
Open the exact address you gave the tracker, with the same host spelling. www.yoursite.com and yoursite.com are different hostnames to any rule that matches on a hostname. Plausible's guide notes the same trap for its checker, which looks only at the exact URL you registered.
3. Your browser or network blocked it
Plausible's guide says it plainly: some visitors use tools that block analytics scripts, including privacy browsers, Pi-hole and corporate firewalls. Its proxy documentation puts the loss at "typically between 5% and 25% depending on your audience." That range is about your visitors in aggregate. For your own test it is binary: either your browser ran the script or it did not.
Test it in a way that removes your setup:
- Open a private window. Extensions are usually off there, but some are allowed in private mode, so check the extensions page.
- Load your site and open DevTools, Network tab, then reload.
- Filter for
t.js. A red entry, a status ofblocked, orERR_BLOCKED_BY_CLIENTmeans an extension or a network filter stopped it. - Switch to a phone on mobile data. A page view that shows up from the phone but not from your laptop points at the laptop or its network.
Tracker blocking is a property of the visitor, not a bug in your install. If a phone on a different network produces a page view and your laptop does not, the install is fine.
4. You told the tracker to ignore you
If you followed advice to keep your own visits out, you may have done it too well. A localStorage flag such as skip-analytics stops the tag from loading in that browser profile, and it stays set until you clear it. A ?me=1 style parameter does the same job for a single visit. Both are covered in our posts on keeping your own visits out and proving an install works in one agent session.
Check from the DevTools Console:
Object.keys(localStorage)
If a skip flag is in the list, remove it with localStorage.removeItem('skip-analytics'), or test from a fresh private window where the flag does not exist.
5. The site key is wrong, and the Network tab told you it was fine
This is the cause that most often fools people who check carefully. You open DevTools, find the beacon request, see 204, and conclude the install works. It might not.
Peeko's ingest endpoint answers 204 to every well formed beacon, whether the key is valid or not. We built it that way so a tracker can never leak whether a key is real. The cost is that a 204 proves the request reached Peeko and proves nothing about the key. The getting started docs say the same: a 204 means the request reached Peeko and does not confirm the key is valid.
So compare keys by eye. Copy the data-site value from the live HTML (the command in check 1 prints it) and the key shown on your dashboard's install card, and diff them. Typos, a key from a different site, and a placeholder like YOUR_SITE_KEY that was never replaced all produce a clean 204 and an empty dashboard.
Two related notes from the docs. A response other than 204 means something between you and Peeko is interfering, which sends you back to checks 3 and 6. And if you test the endpoint yourself with a real key and no Origin header, Peeko refuses it and logs a rejected request on your install card, so send the Origin your site would send. The full test beacon is in the install proof post.
6. A Content Security Policy blocks the script or the beacon
If your site sends a Content-Security-Policy header, it can refuse scripts and network calls to hosts you have not listed. This is less common than the causes above and more common than people expect. The HTTP Archive Web Almanac reports that CSP adoption rose from 18.5% to 21.9% of sites in 2025. If you deploy on a platform or template that adds security headers for you, you may be in that group without having chosen to be.
The symptom is loud if you look. Open the Console and find a red message that begins with "Refused to load the script" or "Refused to connect." Plausible's guide gives the fix in its own terms: add the tracker's domain to the allowed list. For Peeko, the script loads from usepeeko.com and the beacon goes to usepeeko.com/a, so allow https://usepeeko.com in script-src and in connect-src, or in default-src if you rely on the fallback.
7. A consent banner or a script position is holding the tag back
Two quieter causes belong together. If a consent banner or tag manager loads your scripts only after someone clicks accept, then a visit where you have not clicked records nothing, and a tool that checks installs automatically may not see the tag either. Plausible's guide names consent banners as a reason its check cannot verify a script.
Position matters too. Plausible's guide says the snippet must be in the <head> of each page. Put the tag in the layout that wraps every route, not in a single page component, or only that one page will ever report. Peeko is one script tag, it sets no cookie, and it needs no configuration once it is on the page, so if you have a consent step in front of it, the step is yours and not something Peeko requires.
8. You are looking at the wrong thing in the dashboard
Last, because it is the cheapest mistake and the most embarrassing one. Check that:
- You opened the dashboard for the site whose key is on the page. The trial covers one site, but accounts that have moved past the trial often hold several, and a key from site A on site B's domain reports to A.
- The date range includes today and no page or source filter is applied.
- You waited a moment. The getting started docs say a visit shows up within a few seconds, so a visit that is still missing after a minute is not a latency problem. Do not wait an hour for it.
If you work with an AI coding agent, you can take your eyes out of this check. Connect it over MCP, as in connecting Claude Code or Cursor to your site analytics, and have it read the live count back after you load the page. A visit that appears in a read is proof. A 204 is not.
The short order of operations
Run these in sequence and stop when one fails:
curlthe live page and confirm the tag and key are in the HTML.- Load the exact production hostname, not localhost or a preview.
- Open a private window and check the Network tab for
t.js. - Look for a skip flag in localStorage.
- Diff the key on the page against the key on the install card.
- Read the Console for a CSP refusal.
- Check for a consent gate or a tag outside the shared layout.
- Confirm the site, the date range and the filters on the dashboard.
What this list does not cover
Everything above is about the browser tag. AI crawlers do not run JavaScript, so they never show up in a page view count, and an empty dashboard after you load a page tells you nothing about them. Crawler tracking is a separate server side path through the @usepeeko/bot-track middleware, and a new site often sees its first crawler hits within weeks, not minutes, as described in what AI crawlers do on a new site in the first 30 days.
We also have not measured how often each cause above is the real one. If you work through the list and a visit from a second device on a different network still does not appear, the next step is a test beacon with your key and an Origin header, read back through the API, which the install proof post walks through line by line.