Google Universal Commerce Protocol
Measure Universal Commerce Protocol Demand
Universal Commerce Protocol is the open standard co-developed by Google and Shopify so AI agents can discover catalogs and complete checkout—including Google AI Mode and Gemini. Convertmax attributes that demand on first-party events so agent-led commerce does not disappear into organic, bot, or last-click.
The protocol
What Universal Commerce Protocol Is
It is the open standard for agentic commerce—not Convertmax’s convert contract. Convertmax measures it so Google/Shopify UCP demand lands on the same first-party attribution model as web, CRM, and call converts.
An open agentic commerce standard
Universal Commerce Protocol gives agents a common way to discover merchant capabilities and complete shopping journeys—instead of scraping storefronts or automating browsers.
Built for Google and the wider ecosystem
Google uses it to power agentic checkout on AI Mode in Search and Gemini. Shopify, Etsy, Target, Walmart, Wayfair, and others helped shape the protocol so merchants can advertise capabilities once.
Compatible with existing agent rails
The protocol is designed to work with Agent2Agent (A2A), Agent Payments Protocol (AP2), and Model Context Protocol (MCP)—so checkout can travel over REST, MCP, or other bindings merchants already run.
Not Convertmax’s convert contract
Convertmax Unified Conversion Protocol is a different UCP: our first-party event contract for touchpoints, converts, and revenue. Universal Commerce Protocol is an inbound commerce surface we measure and map into that contract.
The measurement gap
Legacy Analytics Never Saw the Agent
Universal Commerce Protocol moves discovery and often checkout off the storefront session. Without protocol-aware first-party events, that revenue looks like a bot spike, a mystery channel, or last-click luck.
Agent catalog fetches look like bots
Shopping agents requesting product and search endpoints inflate sessions or get blocked—so merchandising never sees Universal Commerce Protocol discovery.
Checkout happens off your storefront
When a shopper completes purchase inside Google AI Mode or Gemini, last-click analytics never saw the session that created the order.
UCP-tagged orders have no journey
Commerce platforms may label the order as a UCP channel. Without first-party identity and protocol metadata, you cannot explain which catalog requests, campaigns, or assists led there.
Every agentic protocol looks the same
Universal Commerce Protocol, ACP, and storefront agent integrations collapse into organic, direct, or “AI traffic” unless protocol hints are stored on the convert.
How Convertmax helps
From Agent Discovery to Attributed Revenue
Step 1
Agents discover the merchant
Agents read the merchant’s Universal Commerce Protocol profile and advertised capabilities. Convertmax records those catalog and discovery hits as agent visits—not human sessions.
Step 2
Checkout completes in-protocol or on-site
Purchase may finish inside Google AI Mode, Gemini, or a UCP-capable storefront. Protocol, source, and channel stay attached whether the human landed on your domain or not.
Step 3
Orders map into one convert contract
UCP-tagged orders, carts, and invoices land as Convertmax Unified Conversion Protocol converts—so revenue stays human-first while agentic metadata rides along.
Step 4
Attribute and compare agentic surfaces
Report Universal Commerce Protocol next to ACP, AI referrals, and paid channels. See which protocol actually created closed revenue—not which one generated crawl volume.
In the platform
Protocol-Aware Attribution, Same Revenue Graph
Universal Commerce Protocol hints ride on Convertmax converts. Agent visits stay out of revenue metrics. Human orders stay attributable—next to ACP, AI referrals, and paid channels.
- How much closed revenue came from Universal Commerce Protocol versus ACP or AI referrals?
- Are Universal Commerce Protocol catalog crawls rising before orders show up?
- Which products and collections are agents discovering through the protocol?
- Can finance see UCP-tagged orders on the same first-party journeys as web and CRM converts?
Agentic commerce measurement
Separate agent visits, AI referrals, and human converts across every agentic surface.
Unified Conversion Protocol
Convertmax’s first-party convert contract—the event model Universal Commerce Protocol orders map into.
Ecommerce teams
Attribute store revenue to the campaigns and sessions that created it—including agentic demand.
Get started
Put Universal Commerce Protocol on First-Party Attribution
Convertmax measures Google/Shopify Universal Commerce Protocol on the same convert contract as the rest of your stack—so agentic checkout is revenue you can explain.