Analytiics

Product Introduction

1. Definition: Analytiics is a developer-centric web and product analytics platform designed to be integrated directly into a software development workflow. It is a technical tool that combines traditional web traffic analysis with custom event tracking, funnel analysis, and revenue attribution.
2. Core Value Proposition: It exists to eliminate the friction between analytics implementation and product development. Its core proposition is to make analytics a first-class, type-safe part of the codebase, managed by AI coding agents or developers via CLI, ensuring data accuracy and actionable insights from the first user visit to revenue conversion.

Main Features

1. AI Agent & CLI-First Setup: The product is configured via an AI coding agent prompt or a command-line interface (npx analytiics start). The agent reads the repository, infers the app's domain, runs the CLI, and guides the developer through instrumentation and verification in a single conversation. This automates the creation of the analytics.yaml tracking plan and initial code integration.
2. Code-Embedded Tracking Plan: The core configuration (analytics.yaml) lives in the application's source code. This file defines events, properties, tags (e.g., activation, conversion), and funnels. This enables code review for analytics changes, generates type-safe tracking functions (e.g., track.pagePublished()), and allows CI/CD checks to catch schema mismatches.
3. Anonymous, Cookie-Less Measurement: For privacy-focused analytics, Analytiics measures anonymous traffic without using persistent tracking cookies. It uses a daily rotating identifier to aggregate anonymous visitor data, providing insights into traffic sources and behavior without requiring user consent for cookie tracking.
4. Visit-to-Revenue Attribution: It connects marketing and product interactions to financial outcomes. Revenue can be tracked by importing payment data via a restricted Stripe API integration or sent via the server-side SDK. By matching user or session IDs, it attributes purchases to specific visits, sources, and campaigns.
5. Live Dashboard & Shareable Insights: Projects include a real-time dashboard showing live visitors on a globe, traffic sources, and key metrics. Dashboards or specific widgets can be published to a public URL. The platform also generates shareable snapshot cards (PNG images) of metrics and ranked lists for celebrating milestones or sharing results.

Problems Solved

1. Pain Point: The disconnect between analytics tracking plans and actual code implementation, leading to inaccurate or missing data ("data drift"). Developers often manually instrument events, which is error-prone and not reviewed alongside feature code.
2. Target Audience: Primary users are developers (full-stack, front-end) and engineering teams building web applications, especially in startups and small-to-medium tech companies. Secondary users are product managers who rely on accurate funnels and revenue data.
3. Use Cases: Essential for teams needing to track user activation funnels (e.g., signup to publish), measure the ROI of marketing campaigns by attributing revenue to traffic sources, and maintaining a single source of truth for event schemas across frontend and backend services.

Unique Advantages

1. Differentiation: Unlike traditional analytics tools (e.g., Google Analytics, Mixpanel) where the tracking plan is managed in a separate UI, Analytiics embeds it in the code. Unlike purely code-driven libraries, it provides a full hosted dashboard and AI/CLI tooling for seamless setup and maintenance.
2. Key Innovation: The deep integration of AI coding agents into the setup and instrumentation workflow is a significant innovation. It treats analytics configuration as a software development task, bridging the gap between intent (what to track) and implementation (the actual code), reducing time-to-accurate-data from days to minutes.

Frequently Asked Questions (FAQ)

1. How does Analytiics handle user privacy and GDPR compliance? Analytiics offers a cookie-less measurement mode for anonymous traffic using daily rotating identifiers, reducing the need for cookie consent banners. For identified user tracking, it is the developer's responsibility to implement proper user consent mechanisms and data handling as per their app's privacy policy.
2. Can I use Analytiics with a backend API or mobile app? The primary focus is web analytics via a JavaScript tracker. However, revenue and server-side events can be sent using the Node.js SDK. The documentation does not currently mention dedicated SDKs for mobile native apps (iOS/Android).
3. What happens if I exceed the 25,000 monthly events on the free plan? The free tier includes 25,000 events per month for one project. The product's pricing page indicates that paid plans start at $8/month for increased event volumes and additional projects, suggesting events may be throttled or require an upgrade upon exceeding the limit.
4. How does the Stripe revenue integration work for attribution? You connect a restricted, read-only Stripe API key. Analytiics imports payment events (charges, refunds). To attribute a payment to a visit, you must send a matching user_id or session_id from your app to Analytiics and ensure the same identifier is present on the Stripe customer object or charge metadata.
5. Is my analytics data and tracking plan secure? The tracking plan (analytics.yaml) resides in your private code repository. Event data is transmitted to Analytiics' hosted service. You should review their Privacy and Terms documents for specifics on data encryption, storage, and processing practices.