Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark
Ctrl k
Search…
Sign up
Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark© Dopler. All rights reserved.
Built with Aveiro

Site analytics

Cookieless page views and custom events for your sites and your customers' sites, with a stats API and per-site dashboards.
Updated 4 days ago
Messages
Page comments
Chirio counts visitors, page views and custom events on your websites and apps without cookies. One script tag per site; the numbers show in the dashboard under Analytics and come back from a stats API, so an app can show each of its own customers their site's traffic.

Add a site

In the dashboard, Analytics adds a site and shows its script tag. With an API key:
curl https://chirio.dev/api/v1/sites \
  -H "Authorization: Bearer chirio_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "name": "Acme", "domains": ["acme.com", "*.acme.com"] }'
The answer includes the script tag. Only events from the site's own domains count, so a copied tag on someone else's page records nothing. For an app that gives each of its customers a site, such as a venue or a shop, pass a profileId. Calling POST /api/v1/sites again with a profileId that already has a site updates that site instead of adding another, so you can call it on every setup. GET /api/v1/sites?profileId= lists sites, GET|PATCH|DELETE /api/v1/sites/:id reads, changes or removes one. Deleting a site removes everything it collected.

The script

<script defer src="https://www.chirio.dev/api/analytics/script" data-site="SITE_ID"></script>
It is under 2 KB and stores nothing on the visitor's device: no cookies, no local or session storage, no screen size or other device probing. The visit lives in memory for one page load. A Global Privacy Control signal, a page inside a frame and localhost send nothing.
  • records a custom event. So does a click on any element with .
window.chirio.track("signup_started", { plan: "pro" })
data-chirio-event="name"
  • Calls made before the script loads queue up with window.chirio = window.chirio || { q: [] }; chirio.q.push([name, data]).
  • data-mask="/r/*,/invite/*" replaces a path segment that holds a secret, such as a booking token or an invite code, with * before anything is sent.
  • Read the numbers

    GET /api/v1/sites/:id/stats?days=30 returns visitors, page views, visits, bounce rate and time per visit, a series per day, and the top pages, referrers, devices, browsers, systems, countries and custom events for the last days days (1 to 365, default 30, today included).
    Raw events are kept 30 days; daily totals are kept for good.

    Limits

    Analytics cost no units. Each plan caps the events collected per calendar month across all its sites, and how many sites a workspace holds:
    Plan
    Events per month
    Sites
    Free10,000100
    Indie100,000100
    Studio500,0001,000
    Scale2,000,00010,000
    Past the event cap, new events are dropped until the month turns. Nothing is billed.

    From an agent

    The MCP server has list_sites, create_site (which returns the script tag) and get_site_stats.