# Pulse ยท June 30, 2026 > Google ships two multimodal AI models, Claude Sonnet 5 lands in Snowflake Cortex AI, and BigQuery's conversational analytics reaches GA. Canonical: https://brandonlazovic.dev/pulse/2026-06-30/ Author: Brandon Lazovic Published: 2026-06-30 Note: Compiled retrospectively on July 16, 2026, from sources published on the date this page covers. ## Google launches Nano Banana 2 Lite and Gemini Omni Flash for fast image and video generation Status: Confirmed | Topics: llm-models-agents Google released two new generative models on June 30: Nano Banana 2 Lite, an image model that produces text-to-image outputs in four seconds at $0.034 per 1,000 images, and Gemini Omni Flash, which generates up to ten-second videos from text, image, or video inputs at $0.10 per second. Both ship across Google AI Studio, the Gemini API, and the Gemini Enterprise Agent Platform, and can be chained so an image from Nano Banana 2 Lite feeds Omni Flash for animation. In plain terms: Both are 'generative' models that create new images or video frames from scratch based on a text description, rather than editing or selecting existing stock footage, which is what lets a business plug them into an automated pipeline producing a full batch of ad or product creative instead of hiring a photographer or video editor for each one. Why it matters: Cheap, fast multimodal generation lowers the cost of producing on-page and ad creative at scale, which raises the bar for what counts as differentiated content. Our take: Cheap generation just pushes the production floor down further. The usage data already shows the durable content is the audience-facing and high-judgment work, not the commodity output a model can now produce in four seconds. - [Google Blog](https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-omni-flash-nano-banana-2-lite/) ## Shopify adds custom metafields to inventory transfers Status: Confirmed | Topics: platform-ecommerce, structured-data-schema Shopify's June 30 changelog update lets merchants define and manage custom metafields on inventory transfers from the admin's Metafields and metaobjects settings, then add or edit values directly on the Transfer Create and Transfer Details pages. The Admin GraphQL API exposes the same fields programmatically for automation. Metafields copy over when a transfer is duplicated and can be used as analytics dimensions, supporting lot or serial tracking, logistics detail, and ERP or WMS synchronization. In plain terms: Metafields are custom data fields Shopify lets merchants attach to a record, here an inventory transfer, to store details the built-in fields do not cover. Why it matters: Structured transfer-level data gives merchants cleaner inventory provenance for feed accuracy and fulfillment reporting. Our take: Custom fields moving onto operational objects like transfers, not just products, signals Shopify angling to be the system of record for supply-chain events, not only storefront listings. Watch whether this extends to purchase and fulfillment orders next, because that is where Shopify starts competing with dedicated ERP and inventory tools instead of just feeding them. - [Shopify Changelog](https://changelog.shopify.com/posts/define-and-manage-metafields-on-inventory-transfers) ## Shopify adds an activity log for app pixel data access changes Status: Confirmed | Topics: platform-ecommerce, measurement-analytics Shopify shipped an activity log on June 29 that tracks when and how a third-party app pixel's customer-data access has changed, available on each pixel's detail page inside the Customer events section of the admin. The log records every modification going back to June 3, 2026, giving merchants a full historical record of what data an app can see. It is available to all merchants running app pixels, with no separate setup required. In plain terms: An app pixel is tracking code a third-party app installs on the storefront to collect customer data, the same idea as an ad platform's tracking snippet. Why it matters: Auditable data-access history helps merchants verify privacy compliance across every third-party tracking pixel on the storefront. Our take: A retroactive audit log for pixel data-access changes is the kind of infrastructure privacy reviews have needed for a while, since merchants previously had no reliable way to prove when a vendor's access scope changed mid-relationship. The next test is whether Shopify makes this proactive, surfacing access-scope changes as alerts instead of leaving it as a log merchants have to remember to check. - [Shopify Changelog](https://changelog.shopify.com/posts/view-data-access-changes-with-the-new-app-pixel-activity-log) ## Anthropic brings Claude Sonnet 5 to Snowflake Cortex AI in private preview Status: Confirmed | Topics: ai-data-stack, llm-models-agents Snowflake announced on June 30 that Claude Sonnet 5 is available in private preview inside Snowflake Cortex AI, with Anthropic as launch partner. The model runs within the Snowflake security perimeter and plugs into CoCo, Cortex Agents, Cortex AI Functions, Cortex Inference, and Snowflake CoWork. Snowflake describes Sonnet 5 as approaching Opus-level quality on coding, debugging, analysis, and agentic tasks while running faster and at lower cost. In plain terms: Cortex AI is Snowflake's built-in suite for building and running AI agents and functions directly on data stored in Snowflake, so the data never has to leave Snowflake's systems to be analyzed. Why it matters: Enterprise teams already inside Snowflake's data perimeter get a frontier coding and agent model without moving data outside it. Our take: The story here isn't the model, it's the price: the same cost curve that makes cheap autonomous commerce agents viable is what makes running a near-Opus model at warehouse scale worth it. That's the pattern worth watching with Sonnet 5, and it's arriving inside enterprise data platforms already. - [Snowflake Blog](https://www.snowflake.com/content/snowflake-site/global/en/blog/claude-sonnet-5-snowflake-cortex-ai) ## Snowflake previews Cortex Sense to give enterprise AI agents automatic semantic context Status: Confirmed | Topics: ai-data-stack, llm-models-agents Snowflake announced Cortex Sense on June 30, entering private preview in mid-July 2026. The system automatically builds semantic understanding of enterprise data from existing signals such as past analyst queries, transformation-tool models, and BI metrics, without manual curation, and flags gaps or conflicts for a human to resolve instead of guessing. In Snowflake's own testing, Cortex Sense raised agent accuracy on benchmark questions from 24.1% to 86.3% while cutting per-query cost from $1.76 to $0.59. In plain terms: Cortex Sense is Snowflake's attempt to automatically figure out what your data means, for example what 'active customer' refers to, by learning from how analysts have already queried it, instead of requiring someone to hand-write those definitions. Why it matters: Grounded semantic context for enterprise data matters because missing context, not weak models, is the usual reason warehouse-native agents give wrong answers. Our take: This is the same lesson RAG work keeps teaching: the model is rarely the bottleneck, ungrounded or missing context is. Automating that context instead of leaving it to manual documentation is the right fix, if the 86.3 percent accuracy claim holds up outside Snowflake's own benchmark. - [Snowflake Blog](https://www.snowflake.com/content/snowflake-site/global/en/blog/enterprise-ai-agents-grounded-context) ## Google makes Conversational Analytics in BigQuery generally available Status: Confirmed | Topics: ai-data-stack, llm-models-agents, measurement-analytics Google announced general availability of Conversational Analytics in BigQuery on June 30, letting users query native BigQuery tables, Iceberg lakehouse tables, and cross-cloud sources like Databricks, AWS Glue, SAP, and Salesforce using natural language instead of SQL. The tool runs multi-step analyses with BigQuery AI functions for root-cause analysis, forecasting, and anomaly detection, shows its reasoning and generated SQL, and supports scheduled autonomous agents for proactive monitoring, all under BigQuery's existing governance and security controls. In plain terms: Iceberg lakehouse tables are open-format tables stored in cloud storage rather than inside BigQuery itself, cross-cloud sources are data sitting in other platforms like Databricks or Salesforce, and BigQuery AI functions are built-in SQL functions that call AI models directly for tasks like forecasting or anomaly detection. Why it matters: Natural-language, agent-run analysis at GA lowers the skill floor for ad hoc SEO and revenue analysis directly against warehouse data. Our take: The same discipline applies here as with any hosted BigQuery AI feature: check what the one-line call is actually doing before you trust it, because Google owns the model and the version behind it, not you. - [Google Cloud Blog](https://cloud.google.com/blog/products/data-analytics/conversational-analytics-in-bigquery-now-ga/)