Google Cloud Next ’26: Gemini’s Push Into Marketing Workflows

Google didn’t unveil a new marketing cloud at Next ’26 — it announced something strategically more significant: Gemini embedded directly into the enterprise platforms your marketing team already runs on. According to MarTech’s Pamela Parker, the defining takeaway from the April 2026 conference is Google’s deliberate choice to make Gemini the AI engine inside existing systems — Salesforce, SAP, WPP, ServiceNow — rather than launching another competing point solution. The decision point for most marketing organizations has already shifted: it is no longer “do we adopt Gemini?” It is “are we positioned to use it when it shows up inside tools we already pay for?”

What Happened

Google Cloud Next ’26 took place in April 2026 and generated over 260 announcements across products, customers, and ecosystem partnerships. For marketers, the signal wasn’t in the volume — it was in the pattern. Rather than launching a standalone marketing platform to compete with Salesforce Marketing Cloud or Adobe Experience Platform, Google announced deep integrations across its enterprise partner ecosystem with Gemini Enterprise as the common thread.

Parker’s MarTech analysis identifies nine announcements marketers need to track:

Gemini Enterprise for Customer Experience is the foundational platform underlying most of what was announced. Access runs through Google Cloud contracts — not self-serve signup — which means enterprise procurement is the entry point. Pricing benchmarks and performance data outside controlled pilots were not disclosed at the event.

Universal Commerce Protocol (UCP) is an open standard introduced at Next ’26 that allows retailers to integrate product catalogs and checkout directly into Google’s AI surfaces. Ulta Beauty was announced as among the first adopters, with rollout expected within a month of the conference. Parker notes the protocol primarily benefits Google by positioning its AI products as the default commerce layer — brands adopting UCP are plugging into Google’s ecosystem.

Macy’s “Ask Macy’s” is a conversational shopping assistant built on Gemini Enterprise covering 2.5 million SKUs, reportedly deployed in four weeks. Parker applies warranted skepticism: “four weeks” likely describes a functional demo rather than a production system at scale. Macy’s pre-existing Google Cloud relationship removed significant onboarding friction that most retailers would face.

Home Depot AI Voice Agents represent one of the more credible retail deployments from the conference. A 50-store pilot showed the system understanding customer intent in under 10 seconds — four times faster than traditional phone menu systems, according to the company’s presentation. Full U.S. rollout is planned over the coming year, and store associates reportedly cited higher job satisfaction as routine call volume declined.

WPP and Google Earth AI integrates Google’s geospatial intelligence into WPP Open, enabling campaigns to factor in weather data, foot traffic patterns, and population movement. The significant limitation: this is available only to WPP agency clients — GroupM, Ogilvy, Grey. Independent agencies and in-house teams have no access path at launch.

SAP-Google Marketing Automation brings Joule AI agents into SAP Customer Experience solutions. Marketers set plain-language objectives; agents handle segmentation, personalization, and execution autonomously. This integration is not yet available — it is planned for the second half of 2026, per Parker’s analysis.

Salesforce-Google Partnership expands Agentforce AI agents to operate simultaneously across Slack, Google Workspace, and Salesforce CRM. Some integrations are rolling out now; the full feature set has no confirmed general availability date.

ServiceNow-Google Partnership enables AI agent chains across both platforms. Parker characterizes this as a “partnership with vision rather than concrete facts” at the current stage — few specifics were disclosed.

$750 Million Partner Fund is Google Cloud’s investment in its ecosystem — targeted at agencies, system integrators, and software vendors building on Gemini. This is not a grant program for marketers; it is supply-side infrastructure investment for the Gemini ecosystem.

The competitive context matters: Google Cloud holds third position in cloud infrastructure, trailing AWS and Azure by a significant margin. That position explains why Google is embedding Gemini inside Salesforce, SAP, and ServiceNow rather than building competing platforms — it is routing model capabilities through enterprise relationships Google does not currently own.

Why This Matters

The strategic implication of Next ’26 is not that Google built a better marketing tool. It is that Google is repositioning Gemini as infrastructure — the AI layer inside platforms marketing already depends on. That is a materially different competitive posture from what Microsoft, Salesforce, or Adobe have been executing independently.

Microsoft’s parallel moves confirm that both companies are executing the same strategic thesis at the same time. MarTech’s Constantine von Hoffman reported on April 21, 2026 that Microsoft launched AI Max for Search Campaigns, AI Visibility Features in Microsoft Clarity, and Universal Commerce Protocol support in Merchant Center the same week as Next ’26. The framing from that reporting: “visibility is shifting away from rankings and clicks and toward being selected inside AI-driven experiences.” Microsoft is playing the same game — making its AI the default surface where buying decisions happen — but from its stronghold in search and productivity.

Google’s approach goes further by embedding Gemini into platforms built on competitor infrastructure. The Salesforce deepening is the most telling signal: Salesforce has an active partnership with Microsoft, yet it is simultaneously integrating Agentforce with Google’s stack. That decision signals enterprise-level confidence in Gemini’s model capabilities that was not present 18 months ago. When the company running your CRM routes its own AI agents through Google’s model, your indirect Gemini exposure is underway whether or not you have made a deliberate evaluation.

For marketing teams, this creates three concrete pressure points:

Your vendor stack is becoming an AI decision layer. The SAP-Joule integration is the clearest example: agents will autonomously handle segmentation, personalization, and campaign execution based on plain-language objectives from marketers. That means a system your team already pays for will make decisions that previously required human configuration — running on model outputs, not your team’s judgment. Governance structures, accountability ownership, and review processes need to be designed before that capability ships, not after it activates.

Conversational commerce is moving from experiment to competitive expectation. Macy’s and Ulta Beauty deploying conversational shopping assistants — even in early form — establishes a consumer experience floor. If a competitor’s AI assistant navigates 2.5 million SKUs in natural language and your product discovery still routes to static category pages, the conversion gap becomes commercially visible. The Home Depot pilot data — intent resolved in under 10 seconds versus conventional IVR — demonstrates that the performance delta between AI-native and traditional customer experience is large enough to matter in operations and revenue.

The integration window is six to twelve months. Most of what was announced is not production-ready today. Parker’s analysis is explicit on timelines: SAP integration is H2 2026, the Salesforce full feature set has no GA date, and ServiceNow specifics were not disclosed. The organizations that benefit most will be the ones that spend this window building data readiness, governance frameworks, and integration-ready stacks — activating within weeks of GA while competitors spend the same period getting procurement approved.

The Salesforce State of Marketing Report, cited in MarTech’s AI tool evaluation guide, found that 75% of marketing teams have adopted AI but most still struggle to integrate it in a meaningful way. That integration gap is precisely what the Google-Salesforce and Google-SAP partnerships are designed to close — and precisely where most teams will get stuck when these tools ship if they haven’t done the foundational work first.

The Data

The announcements at Next ’26 span a wide spectrum from live production deployments to aspirational roadmap items. Understanding the maturity and availability of each announcement is the most practically useful exercise a marketer can run on this news.

Sources: MarTech’s Google Cloud Next ’26 analysis and Google Cloud Blog.

The Microsoft-Google parallel on Universal Commerce Protocol is strategically important: both platforms adopted UCP within the same week. That simultaneity signals UCP is becoming industry baseline, not a Google-proprietary lock-in — a critical distinction for brands deciding whether to invest in implementation. MarTech’s April 21, 2026 Microsoft coverage also confirms that Microsoft Clarity now includes AI Visibility Features showing brands how they appear in AI-generated answers and which content gets cited — a capability set that mirrors what Google is building from the Gemini side.

The 75% AI adoption rate with poor integration outcomes from the Salesforce State of Marketing Report contextualizes the real challenge ahead: these Google partnerships are designed to solve the integration problem by embedding AI directly in existing workflows. But embedding AI in existing systems doesn’t automatically solve the underlying data quality and governance issues that cause integration failures. Those remain the marketer’s responsibility to address before the tools arrive.

Real-World Use Cases

Use Case 1: Mid-Market Retailer Deploying Conversational Commerce via UCP

Scenario: A specialty home goods retailer with 60,000 SKUs and a legacy product search experience is watching conversion decline against AI-native competitors. The team has an existing Google Cloud relationship but hasn’t activated Gemini Enterprise for customer-facing use cases.

Implementation: The retailer activates Gemini Enterprise for Customer Experience through their existing Google Cloud contract and implements Universal Commerce Protocol structured data across the product catalog — standardized SKU attributes, pricing tiers, inventory status, and purchase history signals. A conversational product assistant is deployed on-site with fallback to standard category navigation for edge cases. Most of the implementation timeline — per Parker’s Macy’s analysis — is spent on data normalization, not integration work. Teams without a pre-existing Google Cloud relationship should plan eight to twelve weeks; those already on the platform can target four to six.

Expected Outcome: Customers can ask natural-language product questions and receive curated, purchasable recommendations from the full catalog. Conversion rates on AI-assisted sessions should improve versus static search, though specific benchmark lifts were not disclosed in source reporting. Product discovery support queries decline as the conversational layer handles the disambiguation work that previously required human customer service.

Use Case 2: In-House B2B Team Activating Salesforce-Google Agentforce

Scenario: An in-house marketing team at a B2B SaaS company runs Salesforce CRM and Google Workspace for all collaboration. Current campaign segmentation is entirely manual — a two-to-three day process each cycle that limits campaign velocity.

Implementation: With Salesforce-Google integrations currently rolling out, the team connects Agentforce agents to CRM contact records, deal stage data, and engagement history in Salesforce, cross-referenced with campaign briefs in Google Docs and performance data in Google Sheets. Agents draft initial segmentation cuts based on intent signals and surface them in Slack for human review before activation. The key governance step — per MarTech’s AI evaluation framework — is defining upfront which decisions the agent makes autonomously versus which require human approval. Teams should verify which specific features have confirmed availability before building workflows that depend on capabilities still in development.

Expected Outcome: Segmentation draft time compresses from two to three days to same-day, with human review preserving appropriate oversight. Campaign context becomes persistent across tools rather than scattered in separate documents. Over time, the team builds a feedback loop where agent-generated segments are scored against closed deal data, improving model relevance incrementally.

Use Case 3: WPP Agency Client Activating Geospatial Campaign Intelligence

Scenario: A GroupM client running a national QSR (quick-service restaurant) campaign wants to optimize media spend based on real-time foot traffic and weather — not historical DMA averages or static seasonal models.

Implementation: Through WPP Open’s Google Earth AI integration, available to WPP network clients per Parker’s analysis, the agency accesses geospatial layers: foot traffic by geography, weather forecasts, and population movement patterns. Budget allocation rules are configured to weight digital spend toward high-foot-traffic, poor-weather markets where drive-through and delivery intent is highest. OOH placements adjust in markets where foot traffic is trending above baseline. This capability is exclusive to WPP clients — GroupM, Ogilvy, and Grey — with no current access path for independent agencies or in-house teams.

Expected Outcome: Budget allocation becomes dynamic rather than fixed by market — dollars shift toward highest-opportunity contexts on a near-daily basis. For QSR brands where weather is a strong purchase driver, signal-based allocation reduces wasted spend in low-demand windows. The WPP-exclusive nature makes this a network-level competitive differentiator for clients within the WPP ecosystem versus those working with independent agencies.

Use Case 4: Enterprise Team Preparing for SAP-Joule Marketing Automation

Scenario: A manufacturing company’s marketing team runs SAP Customer Experience and is building their H2 2026 technology roadmap. The SAP-Google Joule integration doesn’t exist yet, but the team wants to activate it on launch day rather than starting evaluation after it ships.

Implementation: The team runs a data quality audit against the framework from MarTech’s April 2026 AI tool evaluation guide: identity resolution across customer touchpoints, integration pipeline health, and real-time synchronization capability. They document current segmentation workflows in plain language so they can be translated directly into Joule agent objectives when the integration is live. They also assign explicit accountability ownership over autonomous versus human-reviewed decisions — budget reallocation, message personalization, and campaign triggers each require a defined owner before agents reach production.

Expected Outcome: When SAP-Joule ships in H2 2026, the team activates within weeks rather than months because the data and governance foundations are already in place. The alternative — waiting until the tool ships to start the data audit — costs the same amount of organizational effort but adds three to six months of delay during which competitors are already running. The Salesforce State of Marketing data on integration failures describes exactly what this team is proactively avoiding.

Use Case 5: E-Commerce Brand Monitoring AI Visibility Across Google and Microsoft Surfaces

Scenario: A DTC brand’s e-commerce team is watching organic search visibility erode as AI-generated answers replace traditional search results on both Google and Bing. They need a systematic way to monitor how the brand appears in those AI-generated experiences and identify where the gaps are.

Implementation: The team deploys Microsoft Clarity’s AI Visibility Features — live as of MarTech’s April 21, 2026 reporting — to monitor brand and product appearance in AI-generated answers on Bing and Copilot, including which content gets cited and how competitors are positioned. Simultaneously, they implement Universal Commerce Protocol structured data on their product catalog for both Google AI surfaces and Microsoft Merchant Center. This positions the catalog for AI-native discovery on both platforms without proprietary lock-in to either.

Expected Outcome: A baseline of AI visibility metrics is established and tracked over six to twelve months, driving content optimization toward the formats and attribute structures AI systems surface most reliably. UCP implementation ensures the catalog is structured for AI-native commerce discovery across both major platforms. The team arrives at competitive AI visibility data before the gap with competitors becomes a crisis — not after.

The Bigger Picture

Google Cloud Next ’26 occurred at a specific inflection point in the AI infrastructure race where competitive advantage is shifting from model capability to distribution depth and ecosystem integration. The conference confirmed what Microsoft’s simultaneous announcements made undeniable: AI-native surfaces — Gemini, Copilot — are becoming the primary interface layer between consumers and brands, and controlling that interface means controlling a significant share of commercial discovery.

MarTech’s Microsoft coverage frames the directional shift clearly: “visibility is shifting away from rankings and clicks and toward being selected inside AI-driven experiences.” When AI agents make purchase-adjacent decisions on behalf of users — surfacing products, answering questions, initiating transactions — the traditional channel model for marketing collapses into a single AI-mediated experience. Brands optimized for AI surface selection through structured data, conversational accessibility, and reliable product information will appear more frequently than brands that aren’t, regardless of keyword targeting or bid strategy.

Google’s counter to Microsoft’s enterprise software stronghold is precise and deliberate: rather than building competing platforms, it embeds Gemini inside Microsoft-partnered systems. The $750 million partner fund reflects this strategy explicitly — Google is buying ecosystem depth through investment in the agencies, integrators, and software vendors that hold Microsoft-adjacent enterprise relationships. For marketing agencies, this fund creates a near-term service line opportunity: Google Cloud competency becomes a revenue-generating capability as Google invests in the Gemini-native partner ecosystem.

The Salesforce State of Marketing finding that 75% of teams adopted AI but most cannot integrate it meaningfully defines the real challenge the second wave of AI adoption poses. The first wave was point tools bolted onto workflows. What Next ’26 represents is AI embedded in foundational infrastructure — CRM, ERP, agency platforms. Teams that navigate this wave successfully are not the ones who adopted the most tools in wave one. They are the ones who built clean data pipelines, clear accountability structures, and integration-ready stacks before the capabilities arrived. Those operational investments compound when the tools ship. The absence of them creates months of delay during which the investments made now would have paid off.

What Smart Marketers Should Do Now

1. Map your core marketing platforms against the Gemini integration roadmap.
The inventory worth running right now is not “what AI tools do we use?” but “which of our foundational marketing systems have announced Gemini integrations?” Salesforce, SAP Customer Experience, and ServiceNow all have active Google partnerships with defined roadmaps. If your team runs on any of these, a Gemini-powered capability is arriving in your stack within the next six to twelve months. Understanding what data lives in those systems, how clean it is, and what decisions it currently drives is essential groundwork that takes weeks to complete. Per Parker’s analysis, SAP-Joule is targeting H2 2026. Waiting until it launches to start the data audit is six months of wasted lead time.

2. Implement Universal Commerce Protocol structured data on your product catalog now.
Both Google and Microsoft adopted UCP as the structured data standard for AI-surface product integration, with both confirming support within the same week in April 2026. Any e-commerce or retail team not already implementing this format is leaving AI-native discovery surface on the table. This is immediately actionable — the standard exists, both platforms support it, and your catalog can be structured for it today, regardless of which specific partner integrations have shipped. The cost is a data engineering sprint; the benefit is catalog visibility across both major AI commerce surfaces.

3. Establish AI decision ownership before your vendor enables autonomous agents.
The SAP-Joule integration’s value proposition — agents autonomously handle segmentation, personalization, and execution based on plain-language objectives — is also its governance risk. MarTech’s AI tool evaluation framework identifies this gap explicitly: AI influences decisions around prioritization, messaging, campaign triggers, and budget allocation, and clear human ownership must be established before those decisions are delegated to automation. Build the accountability structure before the tool ships. This is a governance conversation, not a technology conversation — the vendor documentation will not answer it for you.

4. Deploy AI visibility monitoring for your brand on current AI-generated surfaces.
Microsoft Clarity’s AI Visibility Features are live as of MarTech’s April 21, 2026 reporting. They show how your brand appears in AI-generated answers, which content gets cited, and how competitors are positioned in those same results. This data, collected over the next six months, becomes your baseline for understanding AI surface presence before absence becomes a competitive problem. If Clarity is not deployed on your site, that is a half-day implementation. The competitive intelligence it generates on AI citation patterns is actionable for content strategy and structured data prioritization immediately upon deployment.

5. Establish a Google Cloud relationship before you need Gemini Enterprise access.
Gemini Enterprise for Customer Experience runs on Google Cloud contracts — not a self-serve interface. Parker’s analysis notes that Macy’s four-week deployment was partly enabled by the company’s pre-existing Google Cloud customer status. Enterprise procurement cycles for cloud contracts run three to six months. If your organization needs Gemini Enterprise capabilities in Q1 2027, the evaluation and procurement process needs to begin in Q3 2026 — not after your competitors have deployed and are reporting results from production deployments.

What to Watch Next

SAP-Joule Marketing Automation GA date (Q3–Q4 2026): The most commercially significant announcement from Next ’26 for large marketing organizations is the one with the least specificity. SAP has a massive enterprise install base, and autonomous agent execution in SAP Customer Experience would materially change how large-scale marketing operations work. Watch for GA announcements in Q3 and Q4 2026 and prioritize independent performance validation over launch press releases — controlled pilot metrics will not reflect real-world production complexity.

Salesforce-Google full feature set timeline: Some Agentforce-Google Workspace integrations are rolling out now, but the complete feature set has no confirmed GA date. Salesforce’s Dreamforce conference, typically held in September, is the most likely venue for an updated roadmap. The competitive signal to track: whether Salesforce positions the Google integration above or alongside its Microsoft Copilot integrations — that positioning choice reflects where enterprise confidence in Gemini’s model capabilities actually stands.

Universal Commerce Protocol adoption beyond Google and Microsoft: UCP is positioned as an open standard. Over the next six months, watch whether Amazon, Meta, and major DSPs adopt it for AI-agent-native product discovery. Broad platform adoption would make UCP implementation a universal baseline requirement. Limited adoption would keep it a dual-platform play for Google and Microsoft surfaces specifically — still valuable, but not the industry standard it is positioned to be.

Home Depot full U.S. voice agent rollout: The 50-store pilot data — intent resolved in under 10 seconds at four times the speed of traditional IVR — is compelling but inherently selective. The full national rollout planned over the coming year will produce real-world performance data at variance levels that controlled pilots cannot replicate. Home Depot’s earnings calls and investor materials are the data sources to watch for any AI voice agent attribution on customer satisfaction and operational cost metrics.

Independent conversion data from Macy’s and Ulta AI deployments: Both are live; the open question is whether conversion rates, average order values, and return rates move at scale. Neither retailer disclosed specific performance metrics at launch. Watch Q2 and Q3 2026 earnings calls for any attribution of AI assistant impact — those disclosures, not the launch announcements, are what should drive comparable martech investment decisions.

Bottom Line

Google Cloud Next ’26 confirmed that Gemini is becoming enterprise AI infrastructure, not a standalone marketing product to evaluate in isolation. The strategy is deliberate: embed Gemini into the CRMs, ERPs, and agency platforms marketing teams already run rather than compete for separate budget. Most specific integrations announced are six to twelve months from production readiness, but the integration direction is clearly established and the timeline is specific enough to act on now. The conversational commerce deployments at Macy’s, Ulta, and Home Depot are the clearest leading indicators of where consumer expectations are heading — AI-navigable product catalogs and voice-first interfaces are becoming the baseline, not the differentiator. The marketers who benefit from this shift will not be the ones who waited for the tools to arrive; they will be the ones who spent this window building clean data, clear governance structures, and Google Cloud access so they could activate within weeks of GA while competitors spent those same weeks getting procurement approved.