Product Labeling & Merchant Center XML (A/C/X)

Steps

1. Upgrade if needed. Product labels require the product_labels plan feature (Pro / Scale / Enterprise). Trial explicitly excludes Smart product labels.
2. Enable Product Labeling. Open Product Labeling (/app/labels). Turn on “Labeling enabled”. Choose a preset (Conservative, Balanced, Aggressive Growth, Volume Focus) or customize thresholds (default a_min_poas 1.15, default_label C).
3. Run / wait for label sync. The engine pulls Google Ads Shopping performance, assigns A / C / X (also supports B/D and custom letters), and writes catalog_items.label. Stats include promoted_to_A, demoted_to_C, demoted_to_X.
4. Enable Merchant Center XML. Open Merchant Center XML (/app/merchant-center-xml). Enable the feed, note the org feed URL, schedule hour/timezone. When the store has Google Ads, custom_label_0 is the POAS label (A|B|C|D|X); otherwise a default label is used.
5. Pull the feed in Merchant Center. In Google Merchant Center, use the Profit Bid feed URL as a scheduled fetch. Then build Shopping / PMax listing groups on custom_label_0 (scale A, test C, exclude X).

What A / C / X mean in Profit Bid

A — winners (e.g. 30d POAS ≥ a_min_poas with spend/conversion floors; presets tighten or loosen this). C — default / testing band (default_label C). X — exclude band (e.g. high spend with zero conversions, or weak CTR/zero clicks with impression floors). Demotion can move A → default when short-window POAS collapses.

Not a GMC API “sync toggle”

There is no one-click “push labels into Merchant Center via Content API” switch. The production path is: Labeling engine → catalog label → Merchant Center XML custom_label_0 → Merchant Center fetch. Campaign filters read the label after the feed updates.