Getting started
What Peeko is, how the pieces fit together, and the fastest path from nothing to your first numbers.
Peeko is web analytics you can read in about ten seconds: how many people came, which pages they read, where they came from, and what they bought. Sites belong to a team rather than to a person, so one dashboard shows every site the team owns, and inviting somebody costs nothing.
It is cookieless and first party. No cookie is set, so no consent banner is needed for it, and no IP address is ever stored. A visitor is a one way hash of their address and browser: the one the People number counts is re-salted every day, so it cannot follow anybody into tomorrow, and a second one without the date is what lets the dashboard tell a returning visitor from a new one and string a person's page views into a journey. Privacy and your data has both in full.
Put it on your site
One script tag, or one prompt pasted into the agent that built the site. Both are on Install Peeko, along with the eight platforms people ask about most.
<script defer src="https://usepeeko.com/t.js" data-site="YOUR_SITE_KEY"></script>Your real key is filled in for you the moment you create a site, in the install card on the dashboard and in the prompt the command line prints. Every key you see in these pages is a placeholder.
Read the numbers where you already are
Peeko answers in three places, and they all read the same data.
- The dashboard. Sites, ranges, filters, goals, funnels and revenue, in a browser.
- The command line. The same reads with no browser and no install, over
npx. - MCP. The same reads as tools, so the agent that built the site can answer questions about the traffic it brought in.
Check that it is working
Open your own site, then watch the dashboard: a visit shows up within a few seconds. If nothing
arrives, ask the ingest endpoint directly. It answers 204 to every well formed beacon, whether or
not the key is real, so a 204 here proves the request reached Peeko and nothing else.
curl -sS -o /dev/null -w "%{http_code}\n" -X POST "https://usepeeko.com/a" -H "content-type: application/json" --data '{"k":"YOUR_SITE_KEY","p":"/","r":"https://example.com/","sw":1512,"sh":982,"cs":"light"}'Anything other than a 204 came from something between you and Peeko, not from Peeko: the endpoint
answers 204 to a bad key, a disallowed origin and a bot alike, on purpose, so that a tracker can
never leak whether a key is real.
Leave the placeholder key in that command. A request carrying your real key with no Origin
header is a request Peeko recognizes and then refuses, and it lands on your own install card as a
rejected request, which is a confusing thing to find later.
What Peeko does not do
It does not follow people between sites, build profiles, or sell anything about your visitors. There is nothing to sell: the address is hashed with a secret only Peeko holds and is never written down, and what is stored is a truncated hash, queried inside one site and never across customers.