togotogo
Marketplace

analytics

Other

togo product analytics — event tracking, funnels, retention & dashboards

togo-framework
bash
togo install togo-framework/analytics

Install

bash
togo install togo-framework/analytics

A self-hosted, Mixpanel-lite analytics layer inside your togo app: track events, then query volume over time, top events/properties, funnels, retention cohorts, and active users (DAU/WAU) — over a Go API and REST. Ships with a tiny JS snippet to post events from the browser.

Track

go
import "github.com/togo-framework/analytics"

a, _ := analytics.FromKernel(k)
a.Track(ctx, analytics.Event{
	Name:       "order_completed",
	UserID:     "u_123",
	Properties: map[string]any{"plan": "pro", "amount": 49},
})
a.Identify("u_123", map[string]any{"country": "EG"})

Or POST batches to POST /api/analytics/events from the JS snippet.

Metrics

go
a.Volume("order_completed", from, to, analytics.Daily)            // time series
a.TopEvents(from, to, 10)                                         // most frequent events
a.TopProperties("order_completed", "plan", from, to, 10)          // value distribution
a.Funnel([]string{"visit", "signup", "order_completed"}, from, to) // ordered conversion
a.Retention(from, []int{0, 1, 7})                                 // cohort retention
a.ActiveUsers(from, to)                                           // distinct users (DAU/WAU)
a.DashboardSummary(7)                                             // overview snapshot

REST

Method
Path
Purpose
POST/api/analytics/eventsbatch ingest {events:[…]}
POST/api/analytics/identify{user_id, traits}
GET/api/analytics/volumevolume time series (event, bucket=day|hour, from, to)
GET/api/analytics/toptop events, or top values of property
GET/api/analytics/funnelconversion (?step=a&step=b&…)
GET/api/analytics/retentioncohort retention
GET/api/analytics/activeactive users
GET/api/analytics/dashboardoverview
Rows per page
1–8 of 8
Page 1 of 1

See docs/usage.md for the full API + the client snippet.

Configuration

No required env. The default event store is in-memory and bounded (great for dev + recent-window analytics). For durable history, implement the analytics.Store interface against your database (or stream events to a warehouse) and pass it to analytics.New(store).

<div align="center"> <h3>Premium sponsors</h3> <p> <a href="https://id8media.com"><strong>ID8 Media</strong></a> &nbsp;·&nbsp; <a href="https://one-studio.co"><strong>One Studio</strong></a> </p> <p><sub>Support togo — <a href="https://github.com/sponsors/fadymondy">become a sponsor</a>.</sub></p> </div>