October 2026 Summaries

Snowplow’s Agent Intelligence is a paid add-on for Snowplow Cloud and Private Managed Cloud that captures AI-agent traffic at the CDN layer, allowing organizations to measure visits that traditional JavaScript-based analytics often miss. It distinguishes known AI agents by platform, operator, and purpose, including model training, AI search indexing, user-requested page fetches, link previews, and conventional search indexing, while connecting this activity to AI-referred human visits in a Snowflake warehouse. The product helps teams identify pages heavily accessed by agents, content ignored by agents, AI platforms that generate referral traffic, and changes in AI visibility over time, though CDN request counts should be treated as directional lower-bound estimates. Its components include CDN trackers, an agent-classification enrichment, and an incremental dbt analytics package that produces BI-ready tables, complementing rather than replacing client-side tracking. Setup requires a Snowflake warehouse, CDN tracker deployment, enrichment configuration, and execution of the data model, with availability through a 14-day Snowplow trial.

A reference integration for Google’s CX Agent Studio demonstrates agent self-tracking for a fictional luxury-fashion concierge by having the agent call OpenAPI-based HTTP tools that record shopper intent, decision rationale, and unmet catalog constraints as Snowplow events in BigQuery. Because the agent runtime and tools are managed externally, tracking behavior is governed by detailed prompt instructions, while endpoints validate event vocabularies, attach shopper and conversation identities, and return only an acknowledgement so analytics never affects the customer response. Session, user, and per-turn identifiers are injected into tool-call headers through session variables, allowing client-side browsing activity, server-side tool execution, and agent-side reasoning events to be joined across a conversation and traced from recommendations to clicks, carts, and purchases. The implementation highlights operational issues such as parallel tool calls suppressing text responses, immutable published agent versions requiring code-like testing, and widget timing behavior affecting turn IDs. Included BigQuery queries examine context-lookup health, intent confidence, unmet shopper needs, recommendation funnels, and model drift, helping teams refine prompts, tools, catalog coverage, and agent configurations. Although built for Google’s platform, the approach is intended to work with any agent platform supporting OpenAPI tools and session-scoped request variables, while the published demo remains unsuitable for production without stronger security and hardening.