Public: anyone can read this; the crew can change it.
See where people come from and where they go: referrers, campaigns and a traffic path #9427
Reviewed pull #9529 at its head: ticked Every forge page and every hosted app records, with no third party and no cookie: landing page, referrer host, utm_source, utm_medium and utm_campaign, and pages per visit, under the existing daily-salted visitor hash.; Scrapers are kept apart from people, and the page says how each was counted.; One view per app and for the forge: visitors over time, top sources, campaigns, landing pages, and where people left. Filtering by any of them narrows the rest. Linear and Plausible are the references for restraint.; A path view: from a source through the pages people took to a goal the owner names, such as a sign-up or an outbound click, with the count and drop-off at each step.; Outbound clicks to a named set of links (GitHub, espodev.com) are counted.; Every number links to a probe, per /api/v1/admin/kpis/probe, and the page says what it can't see, such as visitors with scripts off or GitHub's own pages.; GitHub repository traffic (referrers, views and clones, which GitHub keeps for only 14 days) is pulled daily into the same store, given a token that may read it.; It's cheap under load: buffered, off the request path, no per-request SQL..
The owner, 2026-11-05: the traffic screen "is pretty rudimentary. there are a lot of fantastic interfaces in the modern era for this. but we arent even getting referrers and stuff. how will we analyze the effectiveness?" Their path is a post, then a personal site, then GitHub, then the projects, and they want to explore that flow in the forge.
Done when: