gmc reports

Query Merchant Center reports. Reporting is a single method — reports.search — that runs a Merchant Center Query Language (MCQL) query against a report view and returns rows. gmc reports gives you both the raw query tool and a canned performance report.

gmc reports performance                       # last 30 days of product performance
gmc reports performance --since 2026-05-01 --until 2026-05-31
gmc reports performance --json                # raw rows
gmc reports query "SELECT clicks, impressions FROM product_performance_view WHERE date BETWEEN '2026-05-01' AND '2026-05-31'"

gmc reports performance

Product performance (clicks, impressions, CTR, conversions) over a date window, from the product_performance_view.

Option	Description
--days <n>	Window size in days, ending today (default 30)
--since <date>	Start date (ISO YYYY-MM-DD); overrides --days
--until <date>	End date (ISO; default today)
--page-size <n>	Max rows per API page

Human output is a date-sorted table; --json emits { "results": [...], "since", "until" } with the raw ReportRows.

gmc reports competitive-visibility

How your domain's visibility compares to competitors in a category, from competitive_visibility_competitor_view. Country and category are required (the view mandates them); the window defaults to the last 30 days.

gmc reports competitive-visibility --country US --category 536
gmc reports competitive-visibility --country US --category 536 --traffic-source ORGANIC --since 2026-05-01 --until 2026-05-31

Option	Description
--country <code>	2-letter report country code, e.g. US (required)
--category <id>	Numeric Google product category id, e.g. 536 (required)
--traffic-source <src>	ADS, ORGANIC, or ALL (default ADS)
--days / --since / --until	Date window (default last 30 days)
--page-size <n>	Max rows per API page

Output is a table of competitor domains with rank, relative visibility, page overlap, and higher-position rate (your own domain is marked); --json for the raw rows.

gmc reports price-competitiveness

Your prices vs the category benchmark per product, from price_competitiveness_product_view (price and benchmark_price are amounts).

gmc reports price-competitiveness
gmc reports price-competitiveness --country US

Option	Description
--country <code>	Filter to a 2-letter report country code
--page-size <n>	Max rows per API page

gmc reports check

A CI gate on a performance metric: it aggregates product_performance_view over the window and exits non-zero if the metric breaches a threshold — so a Shopping performance regression fails your build.

gmc reports check --metric clicks --min 1000          # fail if < 1000 clicks in the last 30 days
gmc reports check --metric ctr --min 0.02             # fail if CTR < 2%
gmc reports check --metric conversions --min 50 --since 2026-05-01 --until 2026-05-31

Option	Description
--metric <name>	clicks, impressions, conversions, or ctr (a fraction, e.g. 0.02 = 2%)
--min <n>	Fail if the metric is below this
--max <n>	Fail if the metric is above this
--days / --since / --until	Date window (default last 30 days)
--page-size <n>	Max rows per API page

At least one of --min/--max is required. Exit 0 within bounds, 1 on breach (CI gate), 2 usage. --json emits { metric, value, min, max, ok, since, until } — min and max are omitted when not passed.

gmc reports query <mcql>

Run any MCQL query and print the result rows (one JSON object per line, then a count) — or --json for { "results": [...] }. This is the escape hatch for views and columns the presets don't cover.

gmc reports query "SELECT clicks, conversions, conversion_value FROM product_performance_view WHERE date BETWEEN '2026-05-01' AND '2026-05-31'" --json

Option	Description
--page-size <n>	Max rows per API page

Exit codes

0 success · 1 metric breach (reports check CI gate) · 2 usage (malformed --since/--until, non-positive --days, bad --page-size) · 3 auth · 5 Merchant API.