Confirmed
EU orders Google to share search data and open Android to AI rivals
The European Commission issued legally binding specification decisions against Google on July 15, 2026, under the Digital Markets Act. Google must share the same anonymized search data it uses to improve its own service with competing search engines, including AI chatbots with search features, under a set pricing formula. Google must also give third-party AI assistants access to core Android functions comparable to Gemini's.
In plain termsThink of it like a utility rule: Google now has to sell rivals access to the same search signals it uses for itself, and let outside AI apps plug into Android the way Google's own Gemini does, at a price regulators set rather than one Google picks.
Why it mattersMandated data sharing with rival search engines and AI chatbots could reshape competitive SOV analysis and how AI-visibility strategy accounts for non-Google search surfaces in the EU.
Our takeData-sharing mandates like this tend to arrive well ahead of the tooling that can use them, so the near-term effect is mostly optionality. Which rival search or AI products actually build on Google's data before enforcement teeth show up is the thing to watch, not the ruling itself.
Confirmed
Google connects Instacart, Canva, and YouTube Music to AI Mode search
Google began rolling out connected apps in AI Mode the week of July 16, 2026, letting US users securely link Instacart, Canva, and YouTube Music directly inside Search. Linked apps let AI Mode add ingredients to an Instacart cart, pull design templates from Canva, and build YouTube Music playlists without leaving the results page, with more partner apps promised soon.
In plain termsIn practice, AI Mode is turning into a single remote control that can reach into apps you already use, so asking it a question can end with groceries added to an Instacart cart or a playlist built in YouTube Music, no app-switching required.
Why it mattersSearch is becoming a checkout and task-completion surface, not just an answer surface, which raises the stakes for product feed and app integration readiness.
Our takeThis is the same 'consolidate into the hub' pattern behind OpenAI killing Atlas: capability keeps landing inside the durable surface itself, so the feed and app plumbing is the safer investment, not any single connected app.
Confirmed
Google connects Calendar to Personal Intelligence in AI Mode
Robby Stein, Google Search's VP of Product, announced on July 15, 2026 that Personal Intelligence in AI Mode now connects to Google Calendar. Users can add invites or meetings to their Calendar directly from AI Mode, and responses become more tailored by accounting for a user's existing schedule. The connection is live now in the US, with more countries to follow, joining earlier Gmail and Photos links.
In plain termsThe mechanism here is Google feeding your calendar into AI Mode's answers, so the same question can get a different response depending on what you already have booked, the same way Gmail and Photos links already let it personalize what it tells you.
Why it mattersCalendar awareness pushes AI Mode responses toward deeper personalization, another sign that generic content competes less well against context-aware assistant answers.
Our takeSame intent-absorption pattern from Brandon's read on Anthropic's Economic Index: as assistant answers get more personalized, generic informational content keeps getting absorbed into the answer itself, and only audience-facing or high-judgment work still earns a click.
Confirmed
Google Ads expands Performance Max product reporting to all networks
Google Ads Help confirms that starting June 2026, Performance Max product reporting expanded beyond Search and Standard Shopping campaigns to cover all networks, including Video, App, and Demand Gen. Advertisers now get a single, comprehensive set of product-level metrics, like cost and conversions, across every eligible campaign type that pulls from Merchant Center. Google warns the change can cause a one-time jump in reported impressions and clicks.
In plain termsPerformance Max is Google's automated ad campaign type that runs across Search, YouTube, Display, and more from one setup, and this update means advertisers can finally see how each individual product performed on every one of those channels instead of just Search and Shopping.
Why it mattersUnified cross-network product reporting changes what channel performance means for ecommerce advertisers reconciling Shopping data against Merchant Center feeds.
Our takeThe one-time reporting jump Google is flagging is the tell. Expect Merchant Center and Google Ads product reports to disagree for a cycle or two after rollout, so reconcile the historical baseline before trusting month-over-month comparisons across networks.
Confirmed
Google will merge Shopping ads and free listing policies into one policy set
Google's Merchant Center announcements changelog states that in September 2026, it will consolidate the separate Shopping ads and free listings policies into a single set of Shopping policies for improved organization and clarity. Some individual policies will continue to apply only to Shopping ads, and Google says it will clearly flag those cases. Google states the change does not introduce more restrictive enforcement or substantive policy changes.
In plain termsRight now Google keeps two separate rulebooks, one for paid Shopping ads and one for free product listings, and in September it collapses them into a single rulebook with a handful of ads-only exceptions still flagged separately.
Why it mattersA merged policy document is a paperwork change for now, but it is worth tracking in September for any quiet scope shifts between paid Shopping ads and free listings.
Our takeSame read as Google's category and sale-duration schema update: consolidation documentation says no substantive changes right up until an exception quietly surfaces, so the thing worth watching in September is exactly which policies stay Shopping-ads-only.
Confirmed
Apache Spark 4.2 released
Databricks announced Apache Spark 4.2 on July 16, 2026, the next release of the dominant open-source data processing engine, now available in Databricks Runtime 19 Beta. The release adds a native semantic layer for defining business metrics once, vector similarity search and geospatial types, and improved Spark Connect embedding, spanning more than 1,900 commits from 260-plus contributors.
In plain termsSpark is the open-source engine behind a large share of large-scale data pipelines, and this release adds built-in support for reusable business-metric definitions, near-match ('similarity') search, and location-based data types.
Why it mattersEngine-level releases decide what data tooling AI pipelines can rely on before the managed platforms catch up.
Our takeThe native semantic layer is the more consequential piece here, not the commit count. Defining a business metric once and reusing it across every downstream tool is the same bet BI vendors have chased for years, now built into the engine itself, and whether it holds up across a real multi-team warehouse rather than a single pipeline is the open question worth tracking before adopting it as the source of truth.
Confirmed
Snowflake details bidirectional Iceberg REST interoperability
Snowflake detailed how its Horizon Catalog implements the Iceberg REST Catalog standard in both directions, letting external engines read and write Snowflake-managed tables using vended, short-lived credentials instead of long-lived IAM keys. Snowflake contrasts this with Databricks Unity Catalog, which it says supports only inbound, read-only access to externally managed Iceberg tables.
In plain termsApache Iceberg is an open table format that lets different data tools read the same underlying tables, and this update lets outside tools not just read Snowflake's tables but write to them too, using temporary access credentials instead of permanent keys.
Why it mattersBidirectional catalog interop reduces lock-in decisions to configuration, which changes how search-data warehouses get architected.
Our takeSnowflake's framing of Unity Catalog as read-only-inbound is a competitive comparison, not a neutral spec reading, so the number worth verifying independently is whether external engines can write back to Snowflake tables in production today or only in a preview tier. If the write path holds up, credential vending over long-lived IAM keys becomes the bigger shift, since it changes how access gets audited across multi-engine lakehouses.