Week 25, 2026
Coverage window 12–18 June 2026
For the interpretation of this week, why a data cloud entering the CDP market, GEO becoming a category, and the summer releases landing all point the same way, see the companion essay: Weekly MarTech Signals That Matter to Me: Part 8, Week 25. This page is the record; the essay is the read.
This week’s record
The headline was Databricks entering martech with CustomerLake, an agentic CDP built natively in the lakehouse, landing in a week of big-platform moves around Salesforce Summer ‘26 go-live and Cannes Lions.
- Databricks launched CustomerLake, an agentic CDP embedded in the lakehouse and governed by Unity Catalog (Private Preview; IAS launch partner).
- GEO/AEO became a category: Adobe Brand Visibility (Semrush-powered), Optimizely’s full AEO platform + Conductor, and Sprinklr LLM Insights all shipped within days.
- Salesforce Marketing Cloud Next Summer ‘26 went live (15 June) with Email Archiving net-new and a slate of previewed features now GA.
- Adobe shipped its June Experience Platform release and a June Journey Optimizer release (live-journey limit doubled to 200, automated email Content check), and moved CX Enterprise Coworker to GA.
- Auditability is becoming table-stakes: Salesforce Email Archiving follows Bloomreach’s two-year Messages Archive the prior week.
What changed this week
| Platform | What changed | Source |
|---|---|---|
| Adobe (Brand Visibility)Launched (Jun 17)GEO / AEO | First GEO product since the Semrush acquisition, combines Adobe LLM Optimizer with Semrush’s AI Optimization tool (~290M real prompts) to manage how brands appear in AI answers. Launched ahead of Cannes Lions. | MediaPost · MarTech |
| Adobe (CX Enterprise Coworker)GA (Jun 10)Agentic AI | Outcomes-based agentic AI orchestrating Adobe enterprise apps across analytics, content, and journey orchestration; built on MCP + Agent2Agent; interoperates with Anthropic, AWS, Google Cloud. (GA Jun 10, catch-up from the prior window.) | Adobe newsroom |
| Adobe Experience PlatformShipped (Jun 16)Product release | June release: “When to activate” export controls (Beta), Azure/Snowflake Private Link for destinations, export arrays as enrichment attributes (Beta), Google Ad Manager 360 + Google Customer Match/DV360 to GA, audience-level reporting for 12 destinations, LAVA source GA, Job Schedules anti-pattern detection, P-TTL/e-TTL health checks, persistent split in Audience Composition. | AEP June 2026 RN |
| Adobe Journey OptimizerShipped (Jun 8–18)Product release | June release: live-journey limit raised 100→200 (Jun 18), automated email Content check with one-click fixes (Jun 18), AI-generated content variants in Simulate (Jun 9), supplemental identifiers for external audiences (Jun 11), enhanced Image-to-HTML converter, AEM Content Fragments improvements. Journey Simulation, Journey Fragments, and path-optimization Targeting graduated to GA. | AJO release notes |
| CordialLaunchedAgentic AI / MCP | AI headless infrastructure: every platform capability exposed as a standard service for any AI agent, buildable via MCP, context services, and CLI. | PR Newswire |
| Databricks (new to watchlist)Beta (Private Preview, Jun 16)Agentic CDP | CustomerLake, agentic CDP built natively on the lakehouse, governed by Unity Catalog: data unification, identity resolution, audience building, campaign automation, activation, with a workforce of agents. Private Preview; IAS launch partner. | Databricks · IAS |
| OptimizelyLaunchedGEO / AEO | Full AEO platform with Agent Visibility Analytics and pre-built agents; partnership with Conductor combining log-based AI-traffic data, citations, mentions, crawl behavior, and page-level visibility. | PR Newswire |
| PegasystemsAnnounced (pre-release)Agentic AI | Pega Customer Engagement Studio, agentic UX for Customer Decision Hub combining Pega + third-party agents; brief-to-live-action with governance. Ships later this year with Pega Infinity ‘26. | Pega |
| Salesforce Marketing CloudGA (go-live Jun 15)Product release | Summer ‘26 go-live: Email Archiving net-new (auto-archives sent emails to the Email Message object for audit/compliance). Now GA from prior previews: AMPscript in MCN, RCS in MCN, MCE MCP Server, Dynamic Email Sender, Salesforce-object merge fields, Real-Time Offer Management. | Salesforce · SalesforceBen |
| SprinklrLaunchedGEO / AEO | LLM Insights, AI-native capability to understand and influence how brands are represented in LLM answers, using real-world prompts, connected to content/knowledge/engagement workflows. | Sprinklr |
No changes this week
(scanned, nothing net-new)
Scanned for the 12–18 June window with no net-new release:
- Adobe Journey Optimizer B2B
- Adobe Marketo Engage: still May ‘26, June release not yet published
- Bloomreach: 1.311 still latest; 1.312 not yet published
- Braze: latest remains 28 May (confirmed via Chrome; no June release)
- CDP Institute / Customer Data Alliance
- Hightouch
- HubSpot: June 15 weekly recap not yet published
- InsiderOne
- Iterable
- Klaviyo: June activity is corporate, not product
- Mailchimp (Intuit)
- MoEngage: launched a print magazine, not a product
- Optimove
- Salesforce Account Engagement
- Segment (Twilio)
- Tealium
Watching next (Week 26)
- Databricks CustomerLake: GA timing, pricing, additional launch partners, competitive response from Salesforce/Adobe/standalone CDPs.
- Adobe Brand Visibility: any Cannes Lions follow-through; GEO competitive moves.
- Salesforce Marketing Cloud Next: post-go-live confirmations; email consent mapping (gradual by 13 July).
- Braze: next release expected late June.
- Bloomreach: changelog 1.312.
- Marketo Engage: June release.
- HubSpot: June 15 weekly recap once published.
How this is compiled. Each edition is assembled from official vendor release notes, changelogs, and corporate newsrooms, with AI assistance for the first-pass scan, then reviewed and edited by me before publishing. Items are checked against the primary source; anything I could not confirm is flagged inline.
Corrections and method notes. Found something inaccurate or out of date? Tell me and I will fix it in the next edition.