June.so

Overview

June.so is a product analytics platform purpose-built for B2B SaaS companies. Unlike general-purpose analytics tools, June.so focuses on company-level and user-level product engagement metrics that matter to product teams — feature adoption rates, activation funnels, retention cohorts, and usage patterns segmented by customer account. The platform integrates with Segment, customer data platforms, and CRM systems to enrich product analytics with business context.

What This Script Does

When June.so's tracking script is deployed within a SaaS application, it captures product usage events at the individual user and company level. The script records actions such as feature interactions, page navigation within the application, session starts and durations, and custom events defined by the product team (e.g., "created_project," "invited_teammate," "exported_report").

The script identifies users through unique user IDs and associates them with company accounts, enabling June.so to aggregate usage data at both the individual and organizational level. It collects user attributes (name, email, role, plan type) and company attributes (company name, industry, employee count, subscription tier) that are passed to it by the host application. This data populates dashboards showing activation funnels, feature adoption curves, retention matrices, and engagement scores.

June.so sets cookies or uses local storage to maintain user identification across sessions within the application. The tracking is focused on in-app product usage rather than marketing website behavior — it is typically installed within the authenticated application, not on public marketing pages.

Consent & Compliance

June.so collects detailed behavioral data about how individual users interact with a SaaS product, including their identity attributes and usage patterns. Under GDPR, this constitutes processing personal data. While the processing serves a legitimate business interest (understanding product usage to improve the service), the depth of individual-level tracking — tying specific feature interactions to named users and their companies — goes beyond basic service operation.

The distinction between "analytics" and "functional" is relevant here. Basic operational metrics (is the service up, are features working) are functional. Detailed user-level behavioral analysis for product strategy purposes is analytics processing that typically requires either consent or a carefully documented legitimate interest assessment.

Should You Block This Without Consent?

Yes. June.so performs detailed user-level behavioral analytics that track individual feature interactions and associate them with identified users and companies. This goes beyond what is strictly necessary for service operation and should be treated as analytics processing requiring consent.