LoginSign Up
← Back to all sparks
J

June

ANALYTICS
Velocity7.5

June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.

product analyticsb2b saascomputed traitscustom objectsintegrations
◆Current state
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
◆Where it's heading
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
◆Prediction
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.

◆Recent moves

  1. 16d ago

    Custom objects available for all

    ⚡ SPARK

    Custom Objects is the move that makes June model-flexible — combined with SQL computed traits and the PostHog source, it's the keystone of the May 2025 B2B push.

  2. 16d ago

    SQL computed traits

    ⚡ SPARK

    SQL computed traits widen the kinds of derived metrics customers can express — health scores, session times, custom formulas — without leaving the platform. Together with Custom Objects, this turns June from a dashboard into something closer to a programmable analytics layer.

  3. 16d ago

    Increased computed traits limits

    Re-anchoring the computed-traits limit on live traits rather than total traits is a small but real change in how customers experience the cap — fewer surprise ceilings as accounts mature, plus better in-product transparency around usage.

  4. 16d ago

    Use PostHog as a data source

    Adding PostHog as a data source acknowledges that customers run both side by side and reframes June as the analytics surface on top of an event store rather than a standalone CDP.

  5. 0y ago

    Custom objects GA (duplicate feed entry)

    Duplicate of the Custom Objects GA announcement from a parallel feed source — same content, different ingestion timestamp.

  6. 0y ago

    Custom objects GA (duplicate feed entry)

    Another duplicate of the Custom Objects GA announcement from the cross-posted feed.