Operations · Analytics

See where your site's visitors come from.

One line in the <head>, and your site traffic shows up: visits, pages, sources, countries, goals and events. No cookie. No identifier is stored in the visitor's browser.

For your agent: paste the llms.txt URL into your agent, and it installs. To sign in to the dashboard, you get a code by email. The dashboard is in Portuguese for now.

Why this exists

Today, seeing your own traffic becomes
A PROJECT.

You only wanted to know where visits come from and which page works. Along the way you get setup, cookies, reports nobody opens and numbers that say zero when nothing was measured. Here the question has an answer on one screen.

  • The script that needs setup before the first number
  • The cookie stored in the visitor's browser
  • The zero that hides a "not measured"

The whole path

Install, read, filter, measure.

One line at the start, and no server to set up.

1 · Install

One line in the <head>, and your site traffic shows up.

Paste the line, or let the installer paste it. It recognizes Next, Vite, Create React App, Astro and plain HTML projects, and shows the change before it saves. In Settings, the site goes from "Aguardando" (waiting) to "Recebendo" (receiving) when the first visit arrives.

html
<script defer
  src="https://analytics.worker.myoperations.click/tracker.js"
  data-site="<id do site>"
  data-spa="auto"></script>

$ npx @ciromaciel/analytics web init --site <id>
→ shows the change before saving

2 · Read

The numbers that answer "how did it go?"

Page views, visits, bounce rate and the median time the page was visible, in a daily series, compared with the previous window. Windows of 7, 30 and 90 days, and up to eight windows back.

dashboard
window      7 · 30 · 90 days
go back     up to 8 windows

visits      distinct visitor in the day
bounce      page view under 15 s
time        median visible time

3 · Filter

Filter the screen by anything.

Where the visit came from, which page it saw, which goal it completed. Filters combine with "and": page, source, UTM campaign, country, device, browser, operating system, goal or event. They run over the records of the last 90 days.

filter
source      = instagram
and page    = /precos
and country = Brazil

→ the whole screen now counts
  only those visits

4 · Goals and events

What matters on your site, counted separately.

A goal has a conversion rate over visits and an optional value, in cents. An event is only a count. They appear in separate lists. The "Medir uma ação" (measure an action) assistant turns a sentence into the name, the code and the request for your agent. It lights up when the name arrives.

javascript
analytics.trackGoal('cadastro')
→ conversion rate over visits

analytics.trackGoal('compra', 4900)
→ with a value, in cents

analytics.trackEvent('abriu-o-video')
→ count only

5 · MCP server

It also measures your MCP server: every tool call, with client, session, latency and error.

An MCP-type site gets a server key, and the installer wraps your server. The report shows calls, sessions, error rate and median latency, by tool, by client, by latency range and by protocol revision.

bash
$ npx @ciromaciel/analytics mcp init --key ask_…
→ wraps the server with withAnalytics
→ shows the change before saving

calls · sessions · error · latency
by tool · by client · by protocol

For the agent

The agent reads the full documentation.

And the documentation says up front what the product does not do.

llms.txt

The full documentation, for the agent to read first

The llms.txt is the full documentation: the script, the routes, the diagnostics and what the product does not do, with a checklist for agents. Paste the URL into Claude Code, Cursor, Codex or Windsurf and ask for the integration. The dashboard opens the same text under "Documentação".

prompt
Read https://myoperations.click/products/analytics/llms.txt
and install Analytics on this site with the installer.

→ finds the project's <head>
→ data-spa="auto" if it is a SPA
→ shows the change before saving

What the agent does, and what it does not

The agent installs, measures and reads the numbers. It never writes.

With the llms.txt, the agent adds the script, creates goals and events and wraps an MCP server. To read the numbers, it connects to the read-only MCP server with the same login as the dashboard: eight tools, none of them write. A routine with no person in front reads with the ark_ read key, which also does not write. The ask_ key only records calls from an MCP server.

scope
install the script       yes, via llms.txt
create goal or event     yes
measure an MCP server    yes, with ask_

read the numbers         read-only MCP (OAuth)
                         or API with the ark_ key
delete or create site    no: dashboard only

The yardstick

What It Does, and What It Does Not Do

The limits, stated before you have to ask. The ones in gray are design choices, and each one has its reason next to it.

How far back filters go

90 days

Filters read per-view records that live 90 days. An hourly cron deletes anything older.

Returning visitor

Not here

The visitor hash changes every day, by design. Without it, there are no visitor cohorts or retention.

Real time

None

There is no live visitors screen. The numbers are daily.

Export

No CSV and no email report

The numbers stay in the dashboard and in the read API, with the login session or the read key.

For the agent

llms.txt and read-only MCP

The agent reads the full documentation, installs the script and reads the numbers through the MCP server. No tool writes: creating and deleting sites happens in the dashboard.

Ad blockers

Can block the script

The script comes from the Analytics worker, with no proxy on your domain. A bot that pretends to be a browser is counted. Only bots that declare themselves are discarded.

Pricing

3, 9 or 99 sites

Free to start: 1 site or MCP server, no card and no time limit. What changes between plans is how many sites the account measures. Reports, filters, goals, events, read keys and the MCP server are in every plan, including the free one. Prices are in Brazilian reais (BRL), charged by Stripe.

FAQ

The Questions, in the Order They Come Up

Found a limit that is not written here?

Talk directly with the person who wrote the code. If you found where it breaks, we want to publish it before the next visitor finds out alone.

Operations · Analytics

One line in the <head>, and your site traffic shows up.

No cookie. No identifier is stored in the visitor's browser.