get_product_performance
Per-product behaviour — views, add-to-cart rate, purchases, units and revenue — joined to catalogue price, type and inventory.
When to use it
To find products that get traffic and no carts, and to rank the catalogue by what it actually earns rather than by what it costs.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
Which products get traffic but no sales?
What is stopping people from buying the blade kit?
How to read the result
- view_to_cart_rate is session-based: the share of sessions that viewed the product and then added it, not an event ratio.
- Per-product add-to-cart rates need roughly 100 product views before they are worth a sentence.
What will make you wrong
Caveats
- revenue_cents is gross — before returns, cancellations and post-purchase edits. Rank by it, but discount before sizing an investment.
- price_cents and total_inventory come from the Shopify sync and are already in the reporting currency.
Parameters
productId
Restrict to one product.
limit
Maximum products to return.
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
dateFrom
Start of the window, YYYY-MM-DD. Inclusive.
dateTo
End of the window, YYYY-MM-DD. Inclusive.
Every tool also accepts merchantId, which resolves from your connection. You never pass it.
What comes back
JSON. These are the top-level keys; date-scoped tools additionally carry a _meta block with the server date and the data coverage envelope.
products
Per product: views, add_to_carts, purchases, units_sold, revenue_cents, view_to_cart_rate, and catalogue fields.
currency
The store's reporting currency.
note
How revenue was converted and what it excludes.