June So

June is product analytics built specifically for B2B SaaS — the key differentiator is company-level analytics. While Mixpanel and Amplitude track users, June tracks companies (accounts) as first-class entities alongside users, providing account-level activation, retention, and churn reports out of the box. For agents tracking SaaS product behavior: the API is Segment-compatible (identify, track, group calls) with June adding automatic company-level aggregation and report generation. Confidence is docs-derived.

REST API at api.june.so (Segment-compatible HTTP API). Identify: POST /identify ({userId, traits: {name, email, plan, ...}}). Track: POST /track ({userId, event, properties: {...}}). Group (company): POST /group ({groupId, userId, traits: {name, domain, plan, ...}}). Page: POST /page. All calls authenticated via write key in Authorization: Basic {base64(writeKey:)} header. Segment SDK compatibility: drop-in replacement for Segment HTTP API.

Write key auth (Segment-compatible Basic auth). Keys from June Workspace settings → Sources → Write Keys. HTTPS enforced. No OAuth2. Workspace-scoped key. Segment SDK users can point to June's endpoint with minimal code change.

Segment-compatible format means well-tested request patterns. Validation errors return 400. Event delivery is fire-and-forget with acknowledgment. June processes events asynchronously; reports update within minutes. June uptime at status.june.so.

june.so/docs covers getting started, Segment integration, company analytics concepts, and SDK guides. Getting started: create workspace, set up a source, first event in under 5 minutes. Segment SDK compatibility lowers migration cost from Segment. Community via June Slack. Free plan with generous event limits for early-stage teams.