Open the Analytics tab on any project to see traffic to its your-project.app.canner.ca hostname (and any custom domain you’ve attached). Because Canner records requests as they pass through the platform, there is nothing to install — no snippet in your <head>, no SDK, no build step.
What you get
- Page views — total and over time.
- Sessions — distinct visits, not raw hits.
- Referrers — where your traffic came from.
- Top pages — the paths visitors actually land on.
How “cookieless” works
Most analytics tie a visitor to a cookie that follows them across sites and over time. Canner doesn’t. A session is identified by hashing request attributes server-side, and that hash rotates on a monthly salt — so the same visitor can’t be re-identified across months, and nothing persistent is written to their browser. That means:
- No cookie banner is required for these analytics.
- No third-party script runs on your visitors’ browsers.
- No cross-site tracking is possible — the identifier only exists within your project, for one month at a time.
Where the data lives
Analytics are processed and stored on Canner’s Canadian infrastructure, alongside the rest of your project — the same data-residency guarantee as your app, database, and files. Nothing is shipped to an external analytics vendor. See data sovereignty for the full model.
When you need more
This view is deliberately lightweight — traffic shape, not product analytics. If you need funnels, custom events, or per-user journeys, run your own instrumentation and store it in a Postgres database, or explore it with Data Workshop.