June.so API
Provides a Segment-compatible event tracking and identification API focused on B2B SaaS metrics, enabling company-level (workspace/account) analytics alongside individual user tracking.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Write key and read key are separate credentials which is a good practice. Keys have no scope granularity within their role. Ensure write keys are never exposed client-side.
⚡ Reliability
Best When
You are building a B2B SaaS product and need company-level product analytics that understand workspace/account hierarchies out of the box without custom instrumentation.
Avoid When
Your product is B2C with millions of individual users and no meaningful account grouping, or you need self-hosted analytics for data residency compliance.
Use Cases
- • Track feature adoption events (e.g., feature_used, report_exported) server-side from a SaaS backend to measure which companies use which features
- • Identify new users and associate them with their company/workspace via a group call so all their events roll up to the account level automatically
- • Send lifecycle events (trial_started, subscription_upgraded, churned) from billing webhooks to build funnel and retention reports in June
- • Query company-level engagement data via the June API to feed a health score into a CRM or CS platform for account management workflows
- • Migrate existing Segment event stream to June by pointing the Segment source to June's Segment-compatible ingestion endpoint with no code changes
Not For
- • Consumer B2C analytics at massive scale where individual user-level funnel analysis (not account-level) is the primary need
- • Real-time alerting or anomaly detection on event streams (June is a reporting platform, not a streaming pipeline)
- • Full data warehouse export or raw event-level SQL querying without a third-party integration
Interface
Authentication
Workspace write key for event ingestion (passed as username in HTTP Basic Auth over HTTPS). Read API uses a separate secret key for querying data.
Pricing
Free tier is generous for early-stage startups. All core B2B analytics features are available on free tier.
Agent Metadata
Known Gotchas
- ⚠ The ingestion API returns HTTP 200 for almost all requests including ones with invalid payloads — agents cannot rely on status codes to confirm event validity
- ⚠ Group (company) calls must be made before any user events for a given company to ensure proper association; out-of-order calls lead to orphaned user events
- ⚠ The Segment-compatibility layer covers track/identify/group but not all Segment spec calls — page and screen events may be silently dropped or ignored
- ⚠ Read API (querying metrics) is separate from the ingestion API and uses a different authentication key; agents mixing both must manage two credentials
- ⚠ Company-level computed metrics (product usage scores) are calculated asynchronously and may lag event ingestion by minutes, affecting real-time dashboards
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for June.so API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.