Product analytics moves from dashboards to agents

Agents became first-class analytics objects

Mixpanel set the visible pace. On 1 Oct it launched documentation for Agent Intelligence and created four related product pages in different languages. On 2 Oct, coverage described outcome analytics for AI agent interactions. On 5, 6 and 7 Oct, further press coverage framed Agent Intelligence as a way for product teams to build, track and measure AI agents. On 8 Oct, Mixpanel added Anthropic product pages in English, Japanese and Korean.

That was not an isolated launch post. The supporting motion arrived across docs, localised pages, press and named AI-adjacent positioning in the same week. Mixpanel also released version 0.3.0 of mixpanel-headless on 2 Oct, with built-in API help and mobile session replays, and version 1.6.0 of its iOS session replay package on 1 Oct and again observed on 8 Oct, adding beta wireframes and a backoff fix.

Mixpanel did not move alone. PostHog released @posthog/ai 8.13.4 on 30 Sep, observed on 2 Oct, and 8.13.5 on 6 Oct. It also released multiple agent skills builds between 3 and 11 Oct. Amplitude created Amplitude-MCP-Analytics-Node on 6 Oct, then Amplitude-AI-Node and Amplitude-MCP-Analytics-Python on 10 Oct, alongside AI industry pages added on 6 Oct and a blog titled What AI Engineers Do on 2 Oct. Statsig created statsig-ai-node on 1 Oct, with the same repository appearing again in the 9 Oct feed.

The SDK surface is the product surface

This fortnight was heavy on client libraries, replay and event plumbing. Amplitude released Amplitude-Kotlin 1.33.0 on 7 Oct with streaming analytics as a separate Maven artefact, then released @amplitude/analytics-browser 2.47.3 and @amplitude/analytics-node 1.5.77 on 7 Oct, followed by 2.47.4 and 1.5.78 on 8 Oct. On 11 Oct, it released experiment-ruby-server 1.10.1 with a fix for including the experiment key on local-eval exposure events.

Amplitude also created repositories for AmplitudeUnified-Swift, Amplitude-Swift, Amplitude-Flutter, Amplitude-Java, AmplitudeStreamingAnalytics-Swift, AmplitudeCore-Swift, AmplitudeSessionReplay-iOS, AmplitudeSessionReplay-Android and an amplitude browser SDK GTM template across the period. The pattern is broad SDK coverage, not a single platform push.

PostHog matched that cadence with posthog-js 1.435.6 on 1 Oct, posthog-js 1.438.2 on 7 Oct, posthog-js 1.438.3 on 8 Oct, @posthog/types 1.415.1 and 1.415.2, and @posthog/cli 0.18.10. It also released an iOS app update on 10 Oct that improved retry behaviour for feature flag requests. Mixpanel added or created repositories for Android, JavaScript, React Native and React Native session replay. Heap released 0.7.9 of its React Native autocapture packages on 6 Oct.

The launch calendar was visible before the launch

The cleanest sequence belonged to Mixpanel. On 1 Oct, the company changed pricing packaging by removing Root cause analysis and Metric Trees from the Enterprise tier, launched Agent Intelligence documentation, created multilingual Agent Intelligence product pages and removed a beta service addendum page. The press wave followed from 5 to 7 Oct. Anyone watching only articles saw the middle act, not the opening move.

Amplitude and PostHog were noisier, but just as legible. Amplitude added and removed product pages on 2, 3, 6, 8, 9 and 10 Oct. A Session Replay product page appeared on 8 Oct and was removed on 9 Oct, before Amplitude added 27 product pages and removed 14 product pages, 12 blog pages and one pricing page on 10 Oct. That is a portfolio edit, not normal housekeeping.

PostHog rewrote the map almost daily. It added 34 documentation pages and 26 product pages on 2 Oct while removing 60 documentation pages. It then added 12 AWS-focused documentation pages on 3 Oct, swapped nine documentation pages on 5 Oct, added 128 documentation pages and removed 133 on 6 Oct, added 15 documentation pages on 8 Oct, added another six on 9 Oct and added six more on 10 Oct while removing 30. The company also launched Broadcasts on 6 Oct and a Lineage tab for endpoint dependencies on 8 Oct.

Paid media confirmed this was not just site maintenance. Amplitude, PostHog and Mixpanel each had 40 Google creatives running in the observed feeds. Amplitude had new creatives observed on 1, 5, 7, 8, 10 and 12 Oct, with some earliest first shown on 2 Sep, 1 Oct, 2 Oct and 16 Jun. PostHog had new creatives observed on 1, 4, 5 and 9 Oct, with earliest first-shown dates including 8 Aug and 10 Sep. Mixpanel had new creatives observed on 8 and 10 Oct, earliest first shown on 6 Oct.

Reliability and packaging stayed in the foreground

The category also produced operational signals. On 3 Oct, Heap reported a major incident in which data was not syncing for the Salesforce integration. The issue had been identified, with no duration provided in the observed event. On 8 Oct, Heap reported a minor incident in which user property data was delayed in Heap Connect syncs for US customers. That incident was resolved after roughly 974 minutes.

Amplitude had its own shorter disruption. On 9 Oct, it reported a minor incident in which BigQuery exports lagged for US users. The incident lasted approximately 91 minutes before resolution.

Package downloads also moved sharply in the week. On 10 Oct, weekly downloads for @statsig/siggy fell from 100,274 to 63,549, down 37 percent. Heap's @heap/heap-javascript-bridge-support fell from 19,911 to 13,058, down 34 percent, and @heap/react-native-heap fell from 1,508 to 960, down 36 percent. These are package download figures, not customer counts, but they sit alongside the week’s heavier emphasis on SDK maintenance and integration reliability.