Google has expanded the Merchant API with reports for purchases made through the Universal Commerce Protocol, including in Search AI Mode and Gemini. The October update also adds information about product videos, warranties and the reasons offers are disapproved. The changes concern stores' technical integration with Merchant Center, from the product data they submit to the measurement of individual stages in a purchase.
The new UCP reports are available in the experimental v1alpha version of the reporting component. Google describes them as programmatic access to the same performance information provided in the Merchant Center UCP analytics dashboard. They cover activity within a UCP checkout integration, with dedicated metrics for interactions, orders and transfers to the merchant's cart.
From a buy button click to a completed order
The reporting component separates two perspectives. The first follows the customer's journey at Merchant Center account level. The second identifies products for which people click a buy button directly on Google surfaces. The offer identifier and product title allow those interactions to be associated with items in the store's catalog.
At account level, merchants can retrieve buy button clicks, successful connections between a customer's Google account and their store account, the rate of those connections and completed purchases. The data includes cancellations, order values and information about the products in completed orders. The metrics describe separate stages of the commercial process.
A cart transferred to the merchant's website has its own measurements: the number of transfers, average cart value and average product count. The data therefore distinguishes purchases completed directly through the Google experience from a checkout process continued on the store's website. A cart transfer is recorded separately from a completed order.
The product-specific view reports buy button clicks for each offer. Its documented fields include the account identifier, customer country, product identifier and product title. The number of clicks measures interaction with the button; sales values and completed purchases are described in the reporting view for the integration as a whole.
Multiple accounts and values in different currencies
Google supports queries for standalone accounts, individual sub-accounts and advanced accounts that manage multiple merchants. With an advanced account, results can be aggregated across all sub-accounts or separated by each merchant's identifier. This distinction enables both an examination of overall activity and an analysis of an individual store.
Every query for either UCP report requires a date filter. Dates refer to the merchant's time zone, while customer country describes the customer's location when the event occurred. For situations in which the country cannot be determined, the API reference specifies the special code ZZ, separate from standard country codes.
The documentation treats volume metrics and monetary values separately. Amounts are returned together with their currency, in structures that include a value expressed in millionths of a currency unit. The number of clicks or account connections does not itself have an associated currency. Combining these categories in a single query can split results by currency and omit rows without purchase values.
For accurate totals, Google describes two separate queries: one for counts and the stages of the commercial journey, and another for order and cart values together with the counts associated with each currency. This separation preserves the distinction between how many interactions took place and the financial value recorded.
Videos, warranties and certification documents
In the products component, the videoLinks attribute accepts URLs for videos associated with an offer. An integration can therefore submit additional video material alongside product images, at the level of individual catalog items. The field is optional and describes the data supplied through the API for that particular product.
Warranty support has been expanded beyond vehicle listings to all products. Warranty durations can be expressed in months or years. The certification structure also receives separate fields for the certification document and the label, including product information sheets and energy labels.
The update list explicitly mentions support for the United Kingdom's Department for Energy Security and Net Zero in energy-efficiency information. The product reference describes European EPREL certifications separately. Document and label information occupy different fields, allowing an integration to submit each resource in its appropriate role.
Disapproval reasons become visible at offer level
Another change concerns the diagnosis of offers affected by an account suspension. Instead of a generic account disapproval notice, certain issues are exposed directly on the affected products. According to Google, this presentation identifies the impact on the offer, marketing method and country. The catalog can therefore be examined in terms of the specific consequences for each product.
The account resource also includes homePageUri, a read-only field that returns the store's homepage address. For notification integrations, subscription listings default to pages of 100 results, with a maximum of 200. A continuation token indicates that further results are available, while preserving the parameters of the original query.
Google has also expanded its explanation of notifications about changes to services associated with accounts. These cover the creation, updating or removal of a service relationship and can target one merchant or all managed accounts. The update therefore brings commercial activity measurement, product descriptions and technical relationship management together within the Merchant Center infrastructure, with the alpha version identified separately for the new UCP reports.
The October package also includes four new reporting views for YouTube Shopping affiliate campaigns: campaign statistics, breakdowns by creator and format, video-level results and product-level results. These components are also in v1alpha. Creator information gains the channel's subscriber count, while content reporting separates platform commissions from seller commissions. A product type field is added for tagged and sold products, supplementing the commercial data available through the same interface.
