Merchant Center UCP hub surfaces separate agentic-commerce analytics

What changed

Google’s developer guide already describes the integration and analytics surface. That documentation predates the November account sighting, so this article records the interface appearing in an account rather than declaring that UCP itself launched this week.

The observed analytics distinguish cart transfers, average cart value and product count from native-checkout measures such as buy-button clicks, purchases and average order value. Account linking is another part of the hub. These are different stages of a shopping journey and should not be added together as though each were a completed sale.

Google’s Merchant Center guidance ties the Buy button to eligible listings carrying the relevant native-commerce checkout attribute. Bia Camargo’s accompanying practical post discusses feed preparation, available stock, shipping and returns. Those checks are implementation context; they do not establish that any merchant can activate native checkout in every country simply by changing one attribute.

For a retail measurement team, the useful distinction is between a shopper handed off to the merchant and a purchase completed through Google’s native checkout. Check which event the report counts before comparing it with website analytics or a sales ledger. Cart value is not realised revenue, and account linking is not a purchase.

Clark receives First contributor credit for the specific account observation, with Camargo credited for the practical follow-up. The original screenshot is retained as interface evidence. Country and account eligibility should be checked against the current official programme guidance before treating the appearance of the hub in one US account as a wider rollout.