Skip to content
Price IntelligencePrice Intelligence home

Integration

Google Shopping price monitoring built on your product feed

Google Shopping price monitoring uses a Merchant Center product feed as the catalogue source for competitor tracking. Feed attributes such as id, GTIN, MPN, brand, price and availability sync in, each item is matched to competitor listings by identifier, and monitoring reports where your price sits against named retailers rather than aggregate benchmarks.

Start free trialOpen the live demo14 days, no credit card, cancel in one click.

Your Merchant Center product feed already contains the identifiers matching needs, which makes it an excellent catalogue source. Connect the account or point at the feed, and every item flows in with its id, GTIN, MPN, brand, price, sale price and availability. Competitor prices come back against each item. Nothing is written into your feed, because your feed price has to keep matching your landing page price.

Why a feed is a good source for Google Shopping price monitoring

A product feed is a cleaned, deduplicated, identifier-rich version of your catalogue that somebody on your team already maintains, because Shopping ads stop serving when it is wrong. That maintenance is exactly what matching wants. Feed items also carry the landing page URL, so competitive comparison happens against the page a shopper actually sees rather than an approximation of it. If your store platform has no direct connection, or your PIM owns the data, the feed is usually the shortest route in.

Pricing analytics — price index by SKU

ProductYour priceMarket avgIndex60-day trend
Aurora H7 Noise-Cancelling Headphones$249.00$258.9096.2
Aurora H7 Noise-Cancelling Headphones — Black$275.83$272.00101.4
Aurora H7 Noise-Cancelling Headphones — Midnight Blue$275.90$278.1999.2
Aurora H7 Noise-Cancelling Headphones — Sand$273.31$265.46103.0
Aurora Buds Pro$149.00$162.5391.7
Aurora Buds Pro — Black$165.68$173.0295.8

Index = your price ÷ average in-stock competitor price × 100. Above 100 means you are priced above the market.

Price index for the Northline Supply demo catalogue. 100 means at market; below 100 means priced under the market average.

What data flows in each direction

Merchant Center integration data flow
DirectionWhat movesNotes
Feed to usItem id, title, description, brand, GTIN, MPN, condition, price, sale price, availability, item group id, product link and image linkRefreshed on the feed schedule you set
Us to youMatched competitor prices and stock, MAP violations with screenshot evidence, price index, position mix and identifier quality reportingEvery refresh cycle on your plan
Us to your feedNothingFeed price must match landing page price, so price changes go to the store and reach the feed on its own cycle
Not requestedCampaigns, budgets, bids, conversions, orders and any customer dataNot part of the connection

The feed is a source, not a destination. Repricing writes to a connected store or exports as CSV, and your feed picks the new price up on its next scheduled fetch.

How to connect Merchant Center

  1. 1

    Link the account or the feed

    Authorise read access to your Merchant Center account, or point at a feed file over a URL or SFTP. Both routes produce the same catalogue. Multiple feeds for multiple countries can be connected as separate price contexts.

  2. 2

    Confirm attribute mapping

    Check that GTIN, MPN and brand are reading from the attributes you expect. Custom or supplemental attributes are mapped here too, which matters if your identifiers live in a supplemental feed rather than the primary one.

  3. 3

    Set your identifier quality baseline

    Look at the coverage report before importing everything. It shows how many items have a valid GTIN, how many rely on MPN and brand, and how many have nothing usable at all.

  4. 4

    Import and review matches

    Matching runs against retailer storefronts and marketplaces. Candidates arrive with confidence scores. Confirm in bulk, correct the rest once, and the corrections feed back into future matching.

  5. 5

    Route alerts and reports

    Send alerts to email or Slack, and pull results through the REST API if you want them in your own reporting.

GTIN quality decides how much manual work you do

A valid GTIN gives an exact join with no review. Everything else costs review time. This is worth auditing before you import, because the fix is usually a data job rather than a monitoring job.

Feed identifier quality and its consequence
Feed stateWhat matching doesWhat it costs you
Valid GTIN on the itemExact identifier join, first passNothing. These match themselves
GTIN missing, MPN and brand presentNarrows on manufacturer part number and brand, then scores on attributesA review pass on the lower-confidence results
GTIN present but wrong or reused across variantsProduces confident matches to the wrong item, which is worse than no matchSilent bad data until someone spots it. Reused GTINs across sizes are the classic case
No identifiers, title onlyTitle, attribute and image comparison with a confidence scoreThe heaviest review load, and the lowest automatic coverage

Illustrative arithmetic: on a 4,000 item feed where 3,000 items carry valid GTINs, roughly 1,000 items reach the scored fallback. At 30 seconds of review each that is about eight hours of work once, and far less on later imports because corrections are remembered.

Competitive visibility the feed alone does not give you

Merchant Center reporting tells you, in aggregate, whether your prices sit above or below what other merchants show for comparable products. That is useful for direction and useless for action, because it does not name the retailer, does not tell you when they moved, and does not carry evidence you can enforce against.

Aggregate feed benchmarks

  • Comparison against an unnamed pool of merchants
  • No timeline showing when a competitor moved
  • No stock status on the competing offer
  • No seller identity, so no way to act on a violation
  • Nothing to export as evidence

Monitoring named sources

  • Named retailer and marketplace listings per item
  • Full price history with capture timestamps
  • Stock status, so you are not chasing an unavailable price
  • Seller identity and repeat-offender tracking for MAP work
  • Timestamped screenshot evidence packets

The two go together. Use feed benchmarks to find categories worth attention, then use monitored sources to see who is doing what. Competitor price analysis covers how to turn that into a position decision, and price index and price positioning explains the index arithmetic.

What the Merchant Center integration does not do

  • It does not write prices, titles or any other attribute into your feed.
  • It does not manage campaigns, budgets or bids.
  • It does not fix disapprovals or resolve policy issues, though identifier problems it reports are often the underlying cause.
  • It does not read conversion, order or customer data.
  • It does not replace a store connection when you want price write-back. Pair it with Shopify or another store connection for that.

Point us at your product feed

Connect Merchant Center, see your identifier coverage, and get matched competitor prices against the catalogue you already maintain. Fourteen days free, no credit card.

Frequently asked questions

How does Google Shopping price monitoring work?

Your Merchant Center product feed is used as the catalogue source. Each item flows in with its identifiers, price and availability, then is matched to competitor listings on retailer storefronts and marketplaces, by GTIN first. Competitor prices, stock and promotions are collected on your plan refresh rate and reported against your own price per item.

Do you write anything back into my feed?

No. Your feed price has to match your landing page price, so changing the feed independently would create a mismatch. Repricing writes to a connected store or exports as CSV. Your feed then picks up the new price on its next scheduled fetch, which keeps the feed and the landing page consistent.

What happens to items with no GTIN?

They still get monitored. Matching narrows on manufacturer part number and brand where those exist, then falls back to title, attribute and image comparison with a confidence score. The result is more review work, not less coverage. The identifier coverage report shows exactly how many items are in that position.

Is this the same as the price competitiveness reporting in Merchant Center?

No. Aggregate benchmarks tell you roughly where your prices sit against an unnamed pool of merchants. Monitoring named sources tells you which retailer is at which price, when it changed, whether they have stock, and who the seller is. The first is a direction indicator; the second is what you act on.

Can I connect feeds for more than one country?

Yes. Each feed is treated as its own price context, so a US feed is never compared against listings priced in another currency or market. Items across all connected feeds count toward the product allowance on your plan, and reporting rolls up into a single account.

Can I use a feed instead of connecting my store?

Yes, and many teams do when a PIM owns the catalogue or the store platform has no direct connection. A feed source gives you full monitoring, matching, MAP evidence and analytics. The only thing it cannot do is receive a price, so pair it with a store connection or a CSV export if you want repricing to land somewhere.

How often does the catalogue update from the feed?

On the fetch schedule you set for the connection, which most teams align with their existing feed schedule. Competitor collection runs on your plan refresh rate, from daily on Starter to hourly on Enterprise. The two are independent, so a slow feed schedule does not slow down competitor price collection.

Start monitoring in the next ten minutes

Connect your store, match your catalogue and get your first competitor comparison in the same session.

14 days, no credit card, cancel in one click.