Product analytics moves down the stack

Product analytics was not quiet. It was unusually infrastructure-heavy. On 30 Oct, Amplitude released @amplitude/analytics-browser 2.49.0 and @amplitude/analytics-node 1.5.82. The same day, it released @amplitude/unified 1.2.0 with a shared network request event factory. On 27 Oct, Amplitude-Swift 1.19.4 landed with network tracking fixes, and on 1 Nov Amplitude-AI-Node 0.24.2 updated event catalog and README documentation.

Mixpanel also pushed into capture plumbing. On 2 Nov, mixpanel-flutter 3.1.0 added the ability to forward web events through the Mixpanel event bridge. On 28 Oct and again on 29 Oct, @mixpanel/react-native-session-replay downloads rose materially, first from 11,850 to 23,736 and then to 31,777. Mixpanel also created mixpanel-react-native, mixpanel-swift and mixpanel-unity repositories across the period.

Heap’s signal was narrower but consistent. On 24 Oct, it released @heap/heap-react-native-autocapture 0.7.10, while downloads for that package rose from 3,826 to 8,441. On 28 Oct, downloads for the same package rose from 7,244 to 19,267, and its Babel plugin moved from 7,768 to 19,005. Statsig was active in server-side foundations too: on 28 Oct it created statsig-server-core, on 29 Oct it added statsig-elixir-core, and statsig-node-vercel rose from 58,284 to 123,881 weekly downloads on 28 Oct before rising again to 166,287 on 29 Oct.

PostHog’s fortnight looked less like a launch cycle and more like a map redraw. On 27 Oct, it added two blog pages, one careers page, two attack comparison pages, eight documentation pages, 38 product pages and three pricing pages, while removing two blog pages, one product page and 51 documentation and pricing pages. On 28 Oct, it added 24 customer pages and removed 34 product pages. On 31 Oct, it added two blog pages, two product pages and 12 documentation pages, while removing ten product pages, one customer page, four documentation pages and one pricing page.

The interesting part is the sequence. A buyer visiting on 26 Oct, 28 Oct and 2 Nov would have seen a different product taxonomy each time. On 2 Nov, PostHog launched a blog page on its transition away from DuckDB, added product pages for correlation analysis, dashboards, data pipelines and demo, added a customers page, and introduced a pricing page for data pipelines. This was not a single homepage refresh. It was repeated repositioning across product, docs, pricing and proof.

The product substance matched the reshuffle. On 23 Oct, PostHog added AI observability for foreground Gemini Interactions calls and WebMCP tool-call analytics. On 29 Oct, it added Flutter SDK capabilities for evaluation contexts, reading all flags in one call and controlling whether flag reads send analytics events. On 30 Oct, it added complete Help Scout conversation syncs and expanded marketing reporting data sources to Meta Ads and LinkedIn Ads. SoundBoost also appeared as a customer, with a new case study published on 31 Oct.

Amplitude’s visible positioning moved hard around AI, mobile and enterprise controls. On 24 Oct, it introduced product pages for events and features including a Java agent for analytics and feature flags. On 27 Oct, it added pages for Android product analytics, React Native product analytics and an upgrade for Statsig. On 28 Oct, it added Android feature flags, surveys and session replay pages. On 29 Oct, it added iOS product analytics, iOS session replay and an enterprise AI event page. On 30 Oct, it introduced nine product pages related to features and releases, including iOS feature flags and advanced segments.

The removals mattered as much as the additions. From 24 Oct to 28 Oct, Amplitude repeatedly removed Wix tracking pages while adding Android, iOS and React Native surfaces. On 30 Oct, the website showed a new call-to-action labelled “Wave” while the prior “AI Agents” button was removed. On 30 Oct, its changelog added Metric Explorer as the chart default, Headless Guides & Surveys management through the Developer API, CLI and MCP, and Enterprise-Managed Auth for Amplitude MCP from 27 Oct.

There was also trust pressure. On 25 Oct, Amplitude reported delayed or blocked event delivery to Amazon Kinesis for about 68 minutes, with no impact recorded. On 27 Oct, it reported a minor data ingestion delay that was resolved after about 75 minutes. On 31 Oct, multiple articles reported a security incident in which customer contact information was exposed due to Amplitude’s handling of data for Coinbase. Coinbase clarified that there was no breach of its systems and that no funds were lost.

Mixpanel made the clearest pricing move of the period. On 30 Oct, it added custom and borrowed properties, plus up to five alerts per project, to the Growth tier. It also added custom data and replay retention policy to the Enterprise tier. That is a packaging signal around governance and replay retention, not merely a feature note.

Its supporting surface changed around the same time. On 29 Oct, Mixpanel created documentation pages for error codes including 400 Bad Request, 401 Unauthorized and 429 Rate Limit Exceeded. On 24 Oct, it had four new Google ad creatives running, with the earliest first shown on 13 Oct and 40 creatives live in total. On 25 Oct, it reported degraded service for requests to decide.mixpanel.com for about 453 minutes, later marked as resolved and in postmortem.

The category pattern is clear. The vendors were not just selling charts. They were tightening event bridges, replay capture, mobile SDKs, server runtimes, data warehouse inputs and pricing entitlements. The front-end analytics page is becoming a thinner slice of the competitive surface.