Google just made checkout native to Google Search, YouTube, and Gemini.

At Google Marketing Live, they announced that Universal Cart part of what they are calling the Universal Commerce Protocol (UCP) is rolling out with Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, and a handful of Shopify merchants including Fenty and Steve Madden.

A shopper searches for a product, adds it to a cart inside Google, and checks out with Google Pay without ever visiting your site. A few taps and done. Google says the merchant remains the merchant of record.

Great! But here’s the thing nobody is writing about.

When the purchase happens inside Google's infrastructure, the conversion event is Google's. Not yours.

If a customer converts inside Google's Universal Cart, none of that happens in the order it usually does. The order record still lands in your systems. Because you stay the merchant of record, a real order is generated in Shopify and the payment shows up as an authorized charge in your processor (Stripe or Shopify Payments). What's missing is the front-end attribution. GA4 and your client-side pixels never fire, because there was no on-site session, so you lose source, medium, and any link to the marketing touch that drove the sale. For the AI-surface view of what happened, Google's Merchant Center becomes your main reference.

And when a platform owns both the ad surface and the conversion reporting, the numbers tend to look very favorable to that platform. I've seen this movie before.

Right now, when a customer buys on your site, you own that event. Your stack sees it, you can cross-reference it, you can audit it and you can send it wherever you want.

With UCP, a chunk of your purchases will happen off your site, inside Google's infrastructure. You'll still get the order in Shopify, but to understand what drove it you'll be leaning on Google's data passback. That passback may be accurate. It may have gaps or lag. You won't know unless you have something to check it against.

Yes, and it comes down to how data moves from Shopify into Klaviyo. The integration is split: order events (Placed Order, Ordered Product) and the customer record sync server-side through Shopify's webhooks, while the behavioral events (Viewed Product, Added to Cart, Started Checkout) come from Klaviyo's onsite JavaScript in the browser.

That split decides what survives a UCP sale. Because you stay the merchant of record, the purchase still creates a real Shopify order, so the server-side half works: Klaviyo ingests the order, matches the profile off the email, and your post-purchase flows, segmentation, and LTV fire normally. The browser half breaks. The purchase never loads your site and the Google cart is not a Shopify checkout, so no Started Checkout fires, which leaves your abandoned cart flow with nothing to trigger on.

So lean on the data you control: the Shopify order. Tag UCP and agentic orders in Shopify so the tag syncs into Klaviyo as a segmentable property, then route those buyers into flows built for them and out of ones that assume on-site behavior. And watch the overlap, since a sale reported by both Google and Klaviyo is the same revenue counted twice.

Google built an explicit cart transfer feature into UCP. If a shopper hesitates inside the Universal Cart, there's a one-click option to transfer the entire cart to your site to complete the purchase. When that happens, the customer lands on your site with a pre-loaded cart and your full stack sees the session.

A shopper who transferred their Google cart to your site is about as warm as it gets. The brands that win here will be the ones who recognize that cart transfer event and treat it differently from a standard session, with dedicated flows, tailored landing experiences, and proper server-side event firing.

The problem is most brands won't have the infrastructure to recognize it. They'll see a session that started with a full cart and treat it like any other direct visit.

One thing the retail press coverage is burying is UCP is not just for organic Search and Gemini surfaces. Google has already wired it into paid inventory.

Brands integrated with UCP can now run Shopping ads on YouTube where the shopper completes the purchase directly inside the ad unit with no click-through to a landing page and no session on your site. The conversion happens inside the ad itself. Same story with Direct Offers on Google Ads, where exclusive promotions feature native checkout so a high-intent searcher can buy the promo item without ever touching your site.

This matters because paid ads were the last place most brands expected to lose the session. You're paying for the click and not getting the visit. The conversion is real but the behavioral data, the on-site engagement, the pixel events, the retargeting signals, none of it fires.

Google also announced a new "AI performance insights" tool in Merchant Center. It shows brands their share of voice on AI surfaces like Search and Gemini.

Meaning, Google is building its own attribution reporting for its own surfaces, and positioning Merchant Center as the source of truth for the AI era. Same playbook but different platform. The ad surface, the checkout, and the reporting tool all belong to Google. When you ask "how am I performing," you're asking Google to grade its own homework.

Whoever controls the AI interface controls the attribution story. That's the line worth sitting with. But that's not a reason to opt out. The incremental reach UCP offers is real for most DTC brands. But it's a reason to treat Google's reported numbers as one signal among several, not the answer.

First, treat your own order data as the source of truth, not Google's dashboard. Because you stay the merchant of record, every UCP sale still produces a real order in Shopify and an authorized charge in your processor. That is your independent baseline. When Google's reported numbers and your order records diverge, your records are what you trust and what you reconcile everything else against.

Second, capture the conversion server-side so you can attribute it. The order arrives, but the session that drove it does not, so client-side pixels and GA4 will not connect the sale to a source. A server-to-server event pipeline keyed off the order lets you tag UCP and agentic orders, pass them to your ad platforms cleanly, and dedupe them against channels like Klaviyo that will also try to claim the win. This is the part most brands will skip and regret.

Third, tag UCP orders and brief your team before the numbers start moving. Shopify attributed revenue, Google reported conversions, and last-touch email credit will not agree, and that is expected. If you flag these orders at the source, the gap becomes a segment you can explain instead of a discrepancy someone burns a quarter chasing.

This is why I don't think the attribution problem gets better over time.

UCP was not just built for human shoppers. It was co-developed alongside Shopify, Target, and Walmart as an open standard that AI agents can speak natively. Google already announced a Gemini agent that browses the web, builds carts, and executes purchases autonomously on the user's behalf. When an AI agent buys on your customer's behalf, there is no browsing session, no clickstream and no browser pixel moment. The journey is invisible by design because there was no human journey. Just an agent that read a prompt, evaluated options, and executed a transaction.

You get the order. But you have no idea what drove it.

Browser-side tracking was already losing ground to privacy changes and cookie deprecation. AI-agent commerce is a different category of problem, and no pixel strategy fixes it, not anytime soon. The only answer is server-to-server data infrastructure that captures the order event regardless of how the front-end session happened.

They're building infrastructure for a world where shoppers never leave Google to buy things, retail is the first category. Hotels and food delivery are next and more will follow.

The brands in the best position here are the ones with clean, independent event pipelines. Not because server-side tracking solves the off-site conversion problem directly, but because having your own data infrastructure means you can audit what the platforms are claiming instead of just accepting it.

Browser-side pixels and platform-reported numbers as your primary source of truth were already a fragile setup. UCP is one more reason to fix that before it matters..

Here to help you win, ✌️

Yiqi