Help
How to see traffic
Your public site has no built-in visitor stats, and GitPress does not store blog page views in its own database. You connect a third party under Analytics in the sidebar; the numbers live in that vendor’s dashboard.
Where config lives
It is written to the private data repo’s gitpress.json, same as the site name and comments. Not GitPress’s cloud database. If you turn off “include on the site,” the IDs you filled in stay; the next build just stops injecting the scripts.
How to connect
- Create a site or property at the vendor and copy the ID or snippet they give you.
- Back in GitPress, open Analytics in the sidebar, fill the matching card, and check “include on the site.”
- Optional: paste their dashboard URL into “board link.” After save, the top of this page can jump there in one tap.
- Save. If the public site’s scripts change, a build runs and takes about a minute.
What you can connect
- Google Analytics: measurement ID, like
G-xxxxxxxx. - Microsoft Clarity: heatmaps and session replay; can run alongside traffic stats.
- Cloudflare Web Analytics: beacon token. Reporting from readers in mainland China may be incomplete.
- Baidu Tongji: copy the site ID after hm.js.
- Umami: Cloud or self-hosted. Website ID is a UUID; self-hosted needs a custom script URL.
- 51.LA: the stats id from their dashboard.
- Custom snippets can be added more than once. Plausible, GoatCounter, and other scripts go here.
If GitPress is down
Analytics scripts on your already-published site report to the third party on their own. After you turn analytics off and rebuild, the site stops calling those vendors. gitpress.net does not count visits to your blog; if it is down, the live blog still opens. Opens of gitpress.net itself are sent to Web Analytics only when this app is deployed on Vercel, and that is separate from the third-party stats on your public site.