Google Shopping Price Tracker & Seller Monitor
Pricing
from $9.00 / 1,000 product query checkeds
Google Shopping Price Tracker & Seller Monitor
Track Google Shopping prices and seller offers by product query and market. Reuse a saved task to compare runs and export new-offer or price-change events. Includes coverage reports; healthy checks are billed even when no change is found.
Pricing
from $9.00 / 1,000 product query checkeds
Rating
0.0
(0)
Developer
Monkey D. Scraping
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 hours ago
Last modified
Categories
Features
Share
Track prices and seller offers for specific products on Google Shopping. Run the same saved Apify task again to find price changes on comparable offers and discover newly observed offers in your selected market.

What changes between Google Shopping runs?
- Run 1 establishes the baseline. Save a task with a product query, country and language. Choose
emitCurrentto see the current offers and save them as the starting point. - Run 2 compares offers. Reuse the same task. If Seller A's comparable offer moves from $299 to $249, the dataset records
price_changed. If Seller B's offer is observed for the first time, it recordsnew_offer. These prices illustrate the workflow. - Check coverage before acting. Later runs return events for verified changes. An empty dataset can be normal. Check query health in
SUMMARY. The Actor retains the last healthy baseline when a check is incomplete. Successfully checked queries are billed even when no event is emitted.
中文用户 / 中文用戶: 简体中文说明 · 繁體中文說明(谷歌购物价格监控、Google Shopping爬虫、竞品价格与卖家监控API)
What does this Google Shopping price tracker do?
- Monitors one or more exact product or product-family queries.
- Tracks public prices and displayed seller names by country and language preference.
- Uses the selected country's Google domain and checks offer currency for these markets: US, CA, AU, NZ, GB, JP, IN, BR, MX, CH, AE, SA, KR, PL, TR, SE, NO, DK, AT, BE, CY, DE, EE, ES, FI, FR, GR, HR, IE, IT, LT, LU, LV, MT, NL, PT, SI and SK.
- Establishes a private baseline for each Saved Task.
- Emits
new_offerwhen a previously unknown seller offer is observed. - Emits
price_changedonly when the same canonical offer has two comparable prices. - Suppresses duplicate events caused by normal ranking churn or an unchanged offer reappearing.
- Keeps the last healthy baseline for each query.
- Supports seller allowlists and blocklists.
- Reports per-query health, coverage, billing, and reconciliation metrics in
SUMMARY.
Why use it?
- Change-focused output — later runs stay empty when nothing verifiable changed.
- Reliable comparisons — product model filtering helps prevent a result for one model from changing the price of another.
- Seller visibility — identify newly observed public resellers without treating every ranking movement as a new seller.
- Monitoring-ready state — Saved Tasks retain known offers between scheduled runs.
- Predictable pricing — pay per successfully checked product query, not per offer or change event.
- Automation-friendly data — connect the dataset and run status to webhooks, Make, n8n, Zapier, Google Sheets, or your own API client.
Quick start
Try the headphone-price example task. Open your own saved task with Sony WH-1000XM5, US market settings and a $0.02 run cap. Its first healthy run returns current offers; run that same task again to compare. SUMMARY shows market consistency and query health. No schedule is created by this example.
Browse all ready-to-run examples → — English and 中文.
1. Create a Saved Task
Open the Actor's Input tab, add the products you want to monitor, choose market preferences, and save the configuration as a Saved Task. A Saved Task is required for comparisons across runs because it gives the monitor a persistent private baseline.
2. Run the first check
Choose one of these first-run behaviours:
- Return current offers now (
emitCurrent) — returns the offers observed now and establishes the baseline. Recommended for the first test. - Create a quiet baseline (
baseline) — establishes the baseline without writing current offers to the dataset.
3. Verify the result before scheduling
Open SUMMARY in the run’s key-value store and confirm query health and observed offers. An empty dataset is expected for a quiet baseline or unchanged offers. A healthy check is billed even when it produces no events.
Run the same Saved Task again to check the comparison workflow. An unchanged result should not produce duplicate offers. Changing initialRun does not reset an existing baseline; use resetState only to deliberately start a new history.
4. Schedule the Saved Task
Attach an hourly, daily, or weekly Apify Schedule to the Saved Task. Later healthy runs emit only verified new_offer and price_changed events.
For most catalogues, start with a daily schedule. Increase frequency only when faster detection justifies the additional query checks.
Example input
{"queries": ["Sony WH-1000XM5"],"countryCode": "us","languageCode": "en","initialRun": "emitCurrent"}
What data does it return?
| Field | Description |
|---|---|
eventType | current_offer, new_offer, or price_changed. |
query | Product query that produced the observed offer. |
countryCode / languageCode | Market preferences used for the public Shopping check. |
productTitle | Public product title displayed in the result. |
sellerName | Public seller name displayed in the result. |
priceText | Current price exactly as observed. |
priceAmount / currency | Parsed comparable price and currency when reliably available. |
previousPriceText | Prior observed price for a verified price_changed event. |
previousPriceAmount / previousCurrency | Prior comparable numeric price and currency. |
productUrl | Public offer or comparison URL when exposed; otherwise null. |
observedAt | ISO timestamp of the current observation. |
Illustrative price-change event
The following synthetic example explains the change-event shape; it is not a measured seller price.
{"eventType": "price_changed","query": "Sony WH-1000XM5","countryCode": "IT","languageCode": "it","productTitle": "Sony WH-1000XM5 Cuffie Wireless","sellerName": "Example Shop","productUrl": null,"priceText": "299,00 €","priceAmount": 299,"currency": "€","previousPriceText": "329,00 €","previousPriceAmount": 329,"previousCurrency": "€","previousObservedAt": "2026-08-02T07:30:00.000Z","observedAt": "2026-08-03T07:30:00.000Z"}
Real current-offer excerpt
Reduced record observed in an owner verification run on 16 October 2026 with US/en preferences. Values are retained from that observation. The internal comparison key is omitted for readability.
{"eventType": "current_offer","query": "Sony WH-1000XM5","countryCode": "US","languageCode": "en","productTitle": "Sony WH-1000XM5 Noise Canceling Wireless Headphones. 42% OFF. Nearby, 10 mi","sellerName": "Best Buy","productUrl": null,"priceText": "$228.00","priceAmount": 228,"currency": "$","previousPriceText": null,"previousPriceAmount": null,"previousCurrency": null,"previousObservedAt": null,"observedAt": "2026-10-16T15:21:31.404Z"}
current_offer is an initial snapshot, not a detected price change, so the previous-price fields are null. currency preserves the observed symbol; it is not an ISO currency code. productUrl is null when the result exposes no usable offer URL. Product titles are source text and can include promotions or location fragments. countryCode and languageCode are result preferences for the Shopping check, not a seller's location. The charge is per successfully checked query, not per offer row.
How monitoring state works
| Run | Expected dataset | Reason |
|---|---|---|
First Saved Task run with emitCurrent | Current public offers | Returns a starting snapshot and establishes state. |
First Saved Task run with baseline | Empty | Quietly establishes state. |
| Later run with no verified difference | Empty | No duplicate or speculative event is created. |
| Comparable price differs | price_changed | Includes the previous and current price. |
| Previously unknown seller offer appears | new_offer | Captures the newly observed public offer. |
| Known offer reappears unchanged | Empty | Ranking churn is suppressed. |
An empty dataset can therefore be a correct, successful outcome. A healthy query check is still billed when it establishes a quiet baseline or finds no changes. The billable unit is a checked query, not a notification. Open the SUMMARY record in the run's key-value store to inspect health status, observed counts, price and seller coverage, baseline status, and billing reconciliation.
Pricing
This Actor uses transparent pay-per-event pricing:
- $0.009 per successfully checked product query (
product-query-checked). - $0.00005 Actor start fee per run at up to 1 GB (one start event per GB, minimum one).
- Platform usage during the run is included. Operations on stored data after the run can have separate platform costs.
- Failed or degraded queries are not charged.
- Offers, new-seller events, and detected price changes have no additional charge.
- A query that successfully retrieves and evaluates Shopping results is charged even when optional seller filters leave no accepted offers.
Examples at the configured tariff, assuming 30 days, one run per scheduled check, all product queries checked successfully in that run, and memory at up to 1 GB. Totals include the Actor start event:
| Monitoring frequency | Runs | Query checks | Total event charges |
|---|---|---|---|
| 1 product checked daily | 30 | 30 | $0.2715 |
| 10 products checked daily | 30 | 300 | $2.7015 |
| 100 products checked daily | 30 | 3,000 | $27.0015 |
| 10 products checked hourly | 720 | 7,200 | $64.8360 |
For a first check of one query, the configured total is $0.00905, whether the healthy check emits offers, creates a quiet baseline or finds no later changes. Extra manual runs, changed inputs and post-run storage operations add to these totals. Set a run spending limit in Apify to cap spending.
Customers can set a maximum total charge for every run. Before starting another paid query, the Actor checks the remaining run budget and stops cleanly when the next query cannot be covered. The SUMMARY record exposes billableQueries, chargedQueries, unbilledQueries, queriesSkippedForBudget, and budgetLimitReached for direct reconciliation.
Automate alerts and downstream workflows
- Apify Schedules — run the same Saved Task hourly, daily, or weekly.
- Webhooks — react when a run succeeds or fails and fetch only its change events.
- Make, n8n, and Zapier — route changes to email, Slack, Google Sheets, Airtable, or a database.
- Apify API — start runs and retrieve datasets from any application.
- MCP and AI agents — expose the Actor as a structured monitoring tool through the Apify MCP server.
For change-only notifications, trigger downstream processing on successful runs and continue only when the default dataset contains at least one item.
Use cases
- Competitor and reseller price monitoring.
- Marketplace seller discovery.
- MAP and channel review queues based on publicly observed prices.
- E-commerce catalogue monitoring across countries and languages.
- Price-change alerts for commercial teams.
- Compact change streams for BI tools, spreadsheets, and data warehouses.
FAQ
Why is a successful run's dataset empty?
After the baseline, an empty dataset normally means no verified new offer or comparable price change was observed. Check SUMMARY to confirm that the queries were healthy.
Do I need a Saved Task?
Yes for monitoring across runs. One-off Actor runs are useful for current snapshots, but Saved Tasks provide the persistent identity used to retain and compare the private baseline.
Are failed searches charged?
The query event is not charged for queries classified as failed or degraded. The Actor start fee still applies to the run. Healthy query checks are charged even when seller filters remove all offers, a quiet baseline is created, or no changes are detected.
How are offers that disappear handled?
Offers that drop out of a later public result set are not reported as removed, so ranking changes do not create false alerts.
When is productUrl null?
productUrl is returned when a public result exposes a usable URL. Otherwise it is null; the Actor never invents a destination.
Can I monitor several countries in one Saved Task?
Each task has one country and language configuration. Create separate Saved Tasks for separate markets so baselines and schedules remain clear.
Do I need a Google account or API key?
No. Proxy access and public Shopping retrieval are handled inside the Apify run.
Support
For questions about a query, open a new item in the Actor's Issues tab with the shared run URL, query, country, language and expected product family. Do not post credentials or private data.
Feature requests for additional countries, seller matching, notification workflows, and richer public destination links are welcome. If the Actor saves you time, a review helps guide future improvements.
Understand a run before using its events
Open Run health report — read this first in Output. The same headline appears in the run status. It explains an empty dataset (quiet baseline, no observed changes, seller filters or budget) and lists each query’s requests, market checks and checkpoint status. SUMMARY.readable provides the same overview for automations.
More e-commerce tools by the same author
- Taobao & Tmall Scraper — products, CNY/USD prices, shops and best sellers from Taobao 淘宝 and Tmall 天猫: compare Google Shopping prices with the Chinese source price.
- Shopify Catalog Monitor — products, variants, SKUs, prices and stock of any Shopify store.
- Google Ads Transparency Scraper — a competitor's Google Search, YouTube and Shopping ads.
Chinese Simplified
中文说明:谷歌购物价格与卖家监控工具(Google Shopping Price Tracker 爬虫 / API)
Google Shopping Price Tracker & Seller Monitor 按商品关键词、国家和语言,监控**谷歌购物(Google Shopping)**上的公开价格和卖家报价。首次运行返回当前报价并建立基准,之后每次运行只输出经过验证的 new_offer(新出现的卖家报价)和 price_changed(调价)事件,可直接用于价格提醒、表格和自动化流程。每成功检查一个商品查询0.009美元,报价和变化事件不另收费,运行期间的平台用量已包含。无需Google账号,无需外部API密钥。
专为跨境电商卖家、出海品牌和渠道管理团队打造:跟踪同款商品在海外谷歌购物上的竞品价格,发现新的经销商和卖家。
为什么选择这款谷歌购物价格监控工具?
- 只输出变化:建立基准后,没有经过验证的变化时数据集为空,不会因为排名波动重复提醒。
- 对比可靠:按商品型号过滤,避免把一个型号的结果误当成另一个型号的调价。
- 卖家可见:识别新出现的公开经销商和卖家,而不是把每次排名变动都当成新卖家。
- 适合定时监控:保存为任务(Saved Task)后,已知报价会在各次运行之间保留。
- 价格可预期:按成功检查的商品查询计费,不按报价条数或变化事件计费;失败或降级的查询不收费。
- 方便自动化:数据集和运行状态可接入Webhook、Make、n8n、Zapier、Google表格或你自己的API客户端。
适用场景
- 竞品价格监控:跟踪竞争对手和经销商在谷歌购物上的商品价格,第一时间收到调价事件。
- 经销商与卖家发现:发现新出现在谷歌购物上销售你品牌或同款商品的卖家。
- 渠道与MAP价格审核:根据公开观察到的价格,整理需要复核的渠道价格清单。
- 跨境电商多市场监控:同一商品分别在美国、英国、德国、日本等市场建立任务,按国家和语言跟踪价格。
- 价格变化提醒:把变化事件推送到邮件、Slack、Google表格、Airtable或数据库,供销售和运营团队使用。
- BI与数据仓库:输出精简的变化数据流,方便导入表格和BI工具。
可以获取哪些数据?
- 事件类型(
eventType):current_offer(当前报价)、new_offer(新报价)或price_changed(调价)。 - 查询与市场:商品查询词(
query),以及使用的国家和语言(countryCode、languageCode)。 - 商品与卖家:谷歌购物上显示的商品标题(
productTitle)和卖家名称(sellerName)。 - 当前价格:页面显示的原始价格文本(
priceText),以及可比较的数值价格和币种(priceAmount、currency)。 - 之前的价格:调价事件中的原价格(
previousPriceText、previousPriceAmount、previousCurrency)。 - 链接:公开的报价或比价链接(
productUrl),无法可靠获取时为null。 - 时间:本次观察时间(
observedAt)。
每次运行的 SUMMARY 记录会报告每个查询的健康状态、观察到的报价数量、价格和卖家覆盖情况、基准状态和计费对账数据。
价格
按事件计费,运行期间的平台用量已包含:
| 内容 | 价格 |
|---|---|
| 每成功检查一个商品查询 | 0.009美元 |
| 每次运行启动费(内存不超过1 GB) | 0.00005美元 |
| 报价、新卖家事件、调价事件 | 不另收费 |
| 失败或降级的查询 | 不收费 |
按30天、所有查询均检查成功计算(含启动费):
| 监控频率 | 运行次数 | 查询检查次数 | 总费用 |
|---|---|---|---|
| 1个商品,每天检查 | 30 | 30 | 0.2715美元 |
| 10个商品,每天检查 | 30 | 300 | 2.7015美元 |
| 100个商品,每天检查 | 30 | 3,000 | 27.0015美元 |
| 10个商品,每小时检查 | 720 | 7,200 | 64.8360美元 |
首次检查一个查询的费用为0.00905美元。健康的查询检查即使没有发现变化也会计费。可为每次运行设置最高费用,预算不足以覆盖下一个查询时,工具会自动停止。
使用方法
- 在 Input 页的 Product queries 中输入要监控的商品,例如
Sony WH-1000XM5。 - 选择 Country(国家)和 Language(语言)。表单中预设了美国、意大利、英国、德国、法国、西班牙、加拿大、澳大利亚、巴西和日本。
- 在 First run 中选择首次运行方式:Return current offers now(立即返回当前报价,推荐首次测试)或 Create a quiet baseline(静默建立基准,不输出当前报价)。
- 可选:设置 Maximum observed offers per query(每个查询最多观察的报价数,1–100,默认30),以及 Seller names to include / Seller names to exclude(只看或排除指定卖家)。
- 将配置保存为任务(Saved Task)并运行。打开
SUMMARY确认查询状态正常后,再次运行同一任务即可对比;确认无误后,可为该任务设置每小时、每天或每周的定时运行。
{"queries": ["Sony WH-1000XM5"],"countryCode": "us","languageCode": "en","initialRun": "emitCurrent"}
也可以直接试用耳机价格示例任务。
中文示例任务: 谷歌购物竞品价格监控:AirPods Pro 2美国卖家与报价
常见问题
需要Google账号或API密钥吗? 不需要。代理和谷歌购物公开数据的获取都在Apify运行中完成。
为什么运行成功但数据集是空的?
建立基准之后,数据集为空通常表示没有观察到经过验证的新报价或可比较的调价。可在 SUMMARY 中确认查询状态正常。
必须保存为任务吗? 跨多次运行监控时需要。任务为工具提供持久的私有基准;单次运行适合获取当前报价快照。
失败的查询会收费吗? 被判定为失败或降级的查询不收费,运行启动费仍会收取。
可以在一个任务里监控多个国家吗? 每个任务对应一组国家和语言设置。不同市场请分别创建任务,基准和定时设置更清晰。
可以通过API、自动化工具或AI智能体调用吗? 可以。支持Apify API、Webhook、Make、n8n和Zapier,也可以通过Apify MCP服务器作为AI智能体的结构化监控工具使用。
中文说明会翻译采集到的数据吗? 不会。中文说明只是使用文档;采集到的数据保持来源的原始语言(商品标题和卖家名称按谷歌购物页面原文呈现)。
其他电商数据工具
- Shopify商品采集与价格监控工具:导出竞品Shopify独立站的商品、变体、SKU、价格和有货状态,每1,000个商品0.40美元。
- 淘宝天猫商品采集工具(Taobao & Tmall Scraper):按关键词、店铺或类目采集淘宝天猫商品与价格,对比谷歌购物售价与国内货源价。
- Google广告采集工具(Google广告透明度中心):按域名或品牌查看竞品在Google搜索、YouTube和Google购物上的广告。
- Monkey D. Scraping 全部工具:更多数据采集工具。
Chinese Traditional
中文說明(繁體):Google購物價格與賣家監測工具(Google Shopping Price Tracker 爬蟲 / API)
Google Shopping Price Tracker & Seller Monitor 依商品關鍵字、國家與語言,監測 Google購物(Google Shopping) 上的公開價格與賣家報價。第一次執行回傳目前報價並建立基準,之後每次執行只輸出經過驗證的 new_offer(新賣家報價)與 price_changed(調價)事件。每成功檢查一個商品查詢0.009美元,報價與變化事件不另收費,平台用量已包含。不需要Google帳號或外部API金鑰。
為什麼選擇這款Google購物價格監測工具?
- 只輸出變化:建立基準後,沒有驗證過的變化時資料集為空,不會因排名波動重複提醒。
- 比對可靠:依商品型號過濾,避免把不同型號誤判為調價。
- 看見新賣家:找出新出現的公開經銷商與賣家。
- 費用可預期:依成功檢查的商品查詢計費;失敗或降級的查詢不收費。
適用場景
- 競品價格監測:追蹤競爭對手與經銷商在Google購物上的價格。
- 經銷商與賣家發現:找出開始販售你品牌或同款商品的賣家。
- 跨境電商多市場監測:同一商品在不同國家分別建立任務,依國家與語言追蹤價格。
- 價格提醒:把變化事件推送到Email、Slack、Google試算表或資料庫,供行銷與營運團隊使用。
使用方法
- 在 Product queries 輸入要監測的商品,例如
Sony WH-1000XM5,並選擇 Country 與 Language。 - 在 First run 選擇 Return current offers now(建議第一次測試使用)或 Create a quiet baseline。
- 儲存為任務(Saved Task)並執行,在
SUMMARY確認查詢狀態正常後再次執行同一任務進行比對,確認無誤後再設定排程。
{"queries": ["Sony WH-1000XM5"],"countryCode": "us","languageCode": "en","initialRun": "emitCurrent"}
中文範例任務: 谷歌购物竞品价格监控:AirPods Pro 2美国卖家与报价
價格
每成功檢查一個商品查詢0.009美元,每次執行啟動費0.00005美元(記憶體不超過1 GB),平台用量已包含;報價與變化事件不另收費。例如10個商品每天檢查,30天合計2.7015美元。
常見問題
需要Google帳號或API金鑰嗎? 不需要,代理與公開資料的取得都在Apify執行中完成。
為什麼執行成功但資料集是空的?
建立基準之後,空資料集通常表示沒有觀察到經過驗證的新報價或調價,可在 SUMMARY 確認查詢狀態。
失敗的查詢會收費嗎? 失敗或降級的查詢不收費,執行啟動費仍會收取。
中文說明會翻譯擷取到的資料嗎? 不會。說明是中文,資料保留來源的原始語言(商品標題與賣家名稱以Google購物頁面原文呈現)。