Agent-led setup and verification
A coding agent can inspect the repository, configure a project, install the tracker, instrument meaningful actions, run validation and code-generation checks, and verify pageviews or events in the dashboard.
Analytiics
Freemium
Analytiics is web and product analytics that a coding agent can set up in an application repository. It tracks visitors, pageviews, declared events, funnels, journeys, and revenue while keeping the tracking plan in code.
Analytiicsとは？
Analytiics is web and product analytics for applications that can be set up and instrumented through a coding agent. It helps teams track acquisition, product activity, customer journeys, funnels, and revenue while keeping event definitions in an analytics.yaml file alongside the code.
The setup workflow can create or reuse a project, install the tracker, generate typed event helpers, and check that real events are delivered. Data can be viewed in dashboards covering traffic sources, campaigns, pages, locations, devices, live visitors, people, journeys, and conversions. Stripe revenue imports and server-side revenue events connect payments with visits and product activity.
The tracker supports script-tag and npm-module installation, as well as CLI-led setup. Anonymous traffic uses a daily rotating identifier without tracking cookies or a persistent anonymous profile. Dashboards can remain private, or selected widgets can be published for sharing.
Analytiicsでできること
Code-based tracking plans
Declare events, properties, tags, and conversion funnels in `analytics.yaml`. Generated typed helpers and validation checks help keep event names and property values aligned with the application.
Web and product analytics
Track built-in web activity such as pageviews and navigation alongside custom product events. Dashboard views include traffic sources, campaigns, pages, locations, devices, live visitors, and funnels.
Journeys, identity, and people views
Identify users with opaque application IDs to connect activity across visits and devices, then inspect recent people, visits, events, and purchases. Anonymous journeys cover the current day, while identified journeys are visible privately.
Revenue attribution
Connect Stripe with a restricted read key to import payments, refunds, and renewals, or send revenue from a backend through the server SDK. Revenue and identity events sent from servers are retained in full when event caps are reached.
Sharing and live visitor display
Keep dashboards private or publish selected widgets at a shareable URL. A live stats pill can show visitors active in the last five minutes, with documented React, CSS, and framework-neutral implementation options.
利用シーン
“Instrument a new application with an agent”
Give a coding agent the setup request so it can inspect the repository, run the CLI, install the tracker, add a manifest, and guide the user through browser sign-in and verification.
“Review analytics changes in pull requests”
Define events and their properties in `analytics.yaml`, generate typed helpers, and use validation or strict drift checks to catch changes that no longer match the declared tracking plan.
“Measure activation and conversion funnels”
Declare meaningful actions such as publishing a page and starting a subscription, then connect those browser and server-side events in a funnel to identify where users drop off.
“Attribute payments to acquisition”
Import Stripe payments, refunds, and renewals with a restricted read key or send revenue from the backend, then connect customers’ visits with their payment activity.
“Share selected traffic insights publicly”
Publish chosen dashboard widgets or add a live visitor pill to a site when a team wants to show traffic activity, while keeping product events, funnels, and revenue private by default.
よくある質問
How can Analytiics be installed?
The tracker can be added with a script tag, imported from `@analytiics/tracker`, or set up through `npx analytiics start`. The CLI can create the project, issue a server write key, scaffold `analytics.yaml`, and install the instrument-agent instructions.
What does the tracker collect automatically?
The documented tracker records the initial pageview, single-page-app navigation through the History API, browser back and forward navigation, outbound link clicks, and flushes data when the page is hidden. Custom events can be sent through the module or generated helpers.
Can Analytiics track revenue?
Yes. Stripe can be connected with a restricted read key to import payments, refunds, and renewals. Revenue can also be sent from a backend with the server SDK; the browser tracking path deliberately does not submit revenue.
Does Analytiics use cookies for anonymous traffic?
Anonymous traffic uses a daily rotating identifier and does not use tracking cookies or a persistent anonymous profile. Users can be identified in the application with opaque user IDs to connect activity across visits and devices.
What happens when an event plan reaches its monthly cap?
The cap is soft and data collection is not switched off. At 80% and 100%, account emails are sent; after 100%, the collector keeps one browser event in ten, in whole sessions. Revenue and identity events from servers are retained in full, and upgrading restores full collection from that point.
クイック情報
- Category
- Web and product analytics
- Primary users
- Developers, product teams, and coding agents
- Setup options
- Script tag, npm tracker module, or Analytiics CLI
- Tracking plan
- `analytics.yaml` with generated typed helpers and validation checks
- Free plan
- 25,000 events per month and 1 project
- Paid plans
- Maker, Studio, and Scale plans with higher event and project limits
Analytiicsの代替品
Entire
entire.io
Git hosting and agent session tracking for developers working with coding agents.
Timeful
www.timeful.io
Timeful is a visual editor for designing web app interfaces on a canvas while generating and synchronizing standard Vue and Tailwind code. It helps developers and UI contributors move between visual editing and repository-based code workflows.
Yoetz
yoetz.dev
Yoetz is a local-first, open-source work ledger that checks completion claims from AI coding agents. It compares the agent’s declared work with host-side records and issues a receipt showing what was verified, the coverage reached, and any open findings.