您可以使用 BigQuery Data Transfer Service for Google Merchant Center 连接器将数据从 Google Merchant Center 加载到 BigQuery。借助 BigQuery Data Transfer Service，您可以安排周期性转移作业，将最新数据从 Google Merchant Center 添加到 BigQuery。
支持的报告
适用于 Google Merchant Center 的 BigQuery Data Transfer Service 支持以下数据：
商品和商品问题
商品和商品问题报告包括通过 Feed 或使用 Content API for Shopping 向 Google Merchant Center 提供的商品数据。此报告还包括 Google 检测到的商品项级别问题。您可以在 Google Merchant Center 中或通过查询 Content API for Shopping 来查看商品和商品问题数据。如需了解如何将此数据加载到 BigQuery，请参阅 Google Merchant Center 商品表架构。
地区商品目录
地区商品目录报告包括有关商品的地区性库存状况和价格替换的更多商品数据。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 地区商品目录表架构。
本地商品目录
本地商品目录包括有关商品的本地商品目录的更多商品数据。此报告包含有关本地价格、库存状况、数量、自提和店内商品位置的数据。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 本地商品目录表架构。
效果
效果报告可提供对广告和非付费商品详情中的效果数据的精细细分。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 效果表架构。
畅销商品
畅销商品报告提供的数据与 Google Merchant Center 界面中的数据相同，并支持回填至多 2 年前的国家/地区或类别的数据。其中包括关于购物广告和非付费商品详情中最受欢迎的商品和品牌的数据，以及您的商品目录中是否有这些商品和品牌。此报告基于 Google Merchant Center 提供的畅销商品报告。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 畅销商品表架构。
价格竞争力
价格竞争力报告（以前称为价格基准报告）包括商品级别属性和价格基准数据，它基于通过 Google Merchant Center 提供的价格竞争力报告中的定义。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 价格竞争力表架构。
价格分析
使用价格分析报告查看商品的建议售价，以及更新商品价格后的效果预测。使用价格分析报告可以帮助您更有效地为商品定价。如需详细了解如何使用此报告中的数据，请参阅使用价格分析报告改善商品定价。如需了解如何将此数据加载到 BigQuery 中，请参阅 Google Merchant Center 价格分析表架构。
产品定位
请在设置转移作业时启用产品定位报告，以便在将 Google 购物中的数据加载到 BigQuery 时公开广告定位信息。如需了解如何将数据加载到 BigQuery 中，请参阅 Google Merchant Center 产品定位表架构。
报告选项
适用于 Google Merchant Center 的 BigQuery Data Transfer Service 支持以下报告选项：
当您将数据从 Google Merchant Center 转移到 BigQuery 时，数据会加载到按日期分区的 BigQuery 表中。数据加载到的表分区对应于数据源中的日期。如果您在同一日期安排多次转移，BigQuery Data Transfer Service 会使用最新数据覆盖该特定日期的分区。同一天的多个转移作业或正在运行的回填不会导致重复数据，其他日期的分区不受影响。
多客户账号 (MCA) 支持
建议具有多个商家 ID 的现有客户配置父级多客户账号 (MCA)。
通过配置 MCA，您可以创建单个转移作业来覆盖您所有的商家 ID。
与使用单个商家 ID 相比，使用 Google Merchant Center MCA 具有多项优势：
您无需再管理多个转移作业，即可为多个商家 ID 转移报告数据。
由于所有商家 ID 的数据都存储在同一个表中，编写涉及多个商家 ID 的查询变得容易得多。
使用 MCA 可以缓解潜在的 BigQuery 加载作业配额问题，因为您的所有商家 ID 数据都将加载到同一作业中。
使用 MCA 的一项可能的缺点是后续查询费用有可能较高。由于您的所有数据都存储在同一个表中，检索单个商家 ID 数据的查询仍然必须扫描整个表。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eThe BigQuery Data Transfer Service for Google Merchant Center automates the scheduling and management of recurring load jobs for various Google Merchant Center reporting data, including products, regional and local inventories, performance, best sellers, price competitiveness, price insights, and product targeting.\u003c/p\u003e\n"],["\u003cp\u003eThis service supports Multi-Client Accounts (MCAs), allowing a single transfer to manage multiple Merchant IDs, simplifying queries and alleviating potential BigQuery load job quota issues, although it might lead to higher query costs due to scanning the entire table.\u003c/p\u003e\n"],["\u003cp\u003eData from Google Merchant Center is loaded into date-partitioned BigQuery tables, with the service overwriting the partition with the most recent data if multiple transfers are scheduled for the same date, ensuring no data duplication and no partition conflict on other dates.\u003c/p\u003e\n"],["\u003cp\u003eDifferent reports have different levels of historical backfill support, ranging from 14 days for products and inventories to 2 years for performance and best sellers, while some, like price competitiveness and price insights, do not offer backfill support.\u003c/p\u003e\n"],["\u003cp\u003eThe Performance report has automatic backfill transfer runs, which means that when a transfer is triggered on any report, two additional transfers are automatically created for the previous two days, correcting data in the past if needed.\u003c/p\u003e\n"]]],[],null,["# Load Google Merchant Center data into BigQuery\n==============================================\n\n|\n| **Preview**\n|\n|\n| This product is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n| **Note:** To get support or provide feedback for Google Merchant Center transfers with BigQuery Data Transfer Service, contact [gmc-transfer-preview@google.com](mailto:gmc-transfer-preview@google.com).\n\nYou can load data from Google Merchant Center to BigQuery using the\nBigQuery Data Transfer Service for Google Merchant Center connector. With the\nBigQuery Data Transfer Service, you can schedule recurring transfer jobs that\nadd your latest data from Google Merchant Center to\nBigQuery.\n\nSupported reports\n-----------------\n\nThe BigQuery Data Transfer Service for Google Merchant Center supports the following data:\n\n### Products and product issues\n\nThe products and product issues report includes product data provided to the Google Merchant Center through feeds or using\nthe Content API for Shopping. This report also includes item level issues detected by\nGoogle for your products. You can view product and product issues data in the\n[Google Merchant Center](https://merchants.google.com/) or by querying\nthe [Content API for Shopping](https://developers.google.com/shopping-content/v2/reference/v2.1/). For information on how this data is loaded into\nBigQuery, see the Google Merchant Center [product table schema](/bigquery/docs/merchant-center-products-schema).\n\n### Regional Inventories\n\nThe regional inventories report includes additional product data about\nregional availability and pricing overrides of your products.For information\non how this data is loaded into BigQuery, see the Google Merchant Center [regional inventories table\nschema](/bigquery/docs/merchant-center-regional-inventories-schema).\n\n### Local Inventories\n\nThe local inventories report includes additional product data about local\ninventory of your products. This report contains data on local pricing,\navailability, quantity, pick-up and in-store product location. For information\non how this data is loaded into BigQuery, see the Google Merchant Center [local inventories table\nschema](/bigquery/docs/merchant-center-local-inventories-schema).\n\n### Performance\n\nThe performance report provides granular segmentation of your performance data\nacross both Ads and Free Listings. For information on how this data is loaded\ninto BigQuery, see the Google Merchant Center [performance table\nschema](/bigquery/docs/merchant-center-performance-schema).\n\n### Best Sellers\n\nThe Best sellers report provides the same data found in the Google Merchant Center UI and lets you backfill the data across countries or categories for\nup to 2 years. This includes data about the most popular products and brands in\nShopping ads and unpaid listings, as well as whether or not you have them in\nyour inventory. This report is based on the [best sellers\nreport](https://support.google.com/merchants/answer/9488679)\navailable through Google Merchant Center. For information on how this data is\nloaded into BigQuery, see the Google Merchant Center [best\nsellers tables schemas](/bigquery/docs/merchant-center-best-sellers-schema).\n\n### Price Competitiveness\n\nFormerly known as the price benchmarks report, the price competitiveness report includes product level attributes and price benchmark data and is based\non the same definitions as the [price competitiveness\nreport](https://support.google.com/merchants/answer/9626903)\navailable through Google Merchant Center. For information on how this data is loaded into\nBigQuery, see the Google Merchant Center [price competitiveness table schema](/bigquery/docs/merchant-center-price-competitiveness-schema).\n\n### Price Insights\n\nUse the price insights report to see suggested sale prices for your\nproducts, and predictions for the performance that you can expect if you update\nyour products' prices. Using the price insights report can help you price your\nproducts more effectively. For more information on how to use the data in this\nreport, see [Improve product pricing with the price insights\nreport](https://support.google.com/merchants/answer/11916926) for more\ninformation on how to use the data in this report. For information on how this\ndata is loaded into BigQuery, see the Google Merchant Center\n[Price Insights table\nschema](/bigquery/docs/merchant-center-price-insights-schema).\n\n### Product Targeting\n\nEnable the Product Targeting report when you set up a transfer to expose Ads\ntargeting information when you load data from Google Shopping into\nBigQuery. For information on how the data is loaded into\nBigQuery, see the Google Merchant Center [Product Targeting table schema](/bigquery/docs/merchant-center-product-targeting-schema).\n\nReporting options\n-----------------\n\nThe BigQuery Data Transfer Service for Google Merchant Center supports the following\nreporting options:\n\nData ingestion\n--------------\n\nWhen you transfer data from Google Merchant Center into BigQuery, the data is loaded into BigQuery tables that are partitioned by date. The table partition that the data is loaded into corresponds to the date from the data source. If you schedule multiple transfers for the same date, BigQuery Data Transfer Service overwrites the partition for that specific date with the latest data. Multiple transfers in the same day or running backfills don't result in duplicate data, and partitions for other dates are not affected.\n\n\u003cbr /\u003e\n\nMulti-client account (MCA) support\n----------------------------------\n\nExisting customers with multiple Merchant IDs are encouraged to configure a\nparent [Multi-Client Account (MCA)](https://support.google.com/merchants/answer/188487).\nConfiguring an MCA lets you create a single transfer for all your Merchant\nIDs.\n\nUsing Google Merchant Center MCAs provides several benefits over using\nindividual Merchant IDs:\n\n- You no longer need to manage multiple transfers to transfer reporting data for multiple Merchant IDs.\n- Queries involving multiple Merchant IDs are much simpler to write because all Merchant ID data is stored in the same table.\n- Using MCAs alleviates potential BigQuery load job quota issues because all your Merchant ID data is loaded in the same job.\n\nOne possible disadvantage of using MCAs is that your subsequent query costs are\nlikely to be higher. Because all of your data is stored in the same table,\nqueries that retrieve data for an individual Merchant ID must still scan the\nentire table.\n| **Note:** The BigQuery Data Transfer Service pulls reports for all listed Merchant IDs. If there are no products in Google Shopping for a specific day, you may not see Merchant IDs in the BigQuery table.\n\nIf you are using an MCA, the MCA ID is listed under `aggregator_id` and the\nindividual sub-accounts are listed under `merchant_id`. For accounts that\ndon't use an MCA, `aggregator_id` is set to `null`.\n\nLimitations\n-----------\n\nSome reports might have their own constraints, such as different windows of\nsupport for historical backfills. The following sections describe the\nlimitations for each report.\n\n**Historical Backfills Support**\n\nNot all reports support historical backfills in the same way. The following are\na list of reports and the level of support for historical backfills.\n\n- Products and Product Issues - 14 days\n- Local Inventories - 14 days\n- Regional Inventories - 14 days\n- Performance - 2 years\n- Best Sellers - 2 years\n- Price Competitiveness - No backfill support\n- Price Insights - No backfill support\n\n**Automatic Backfill Transfer Runs**\n\nThe Performance report can have latencies in \"today's\" data. Therefore, when a\ndata export is requested, data might update up to 3 days in the past to account\nfor corrections.\n\nTo support this functionality, whenever a transfer is triggered on any report,\ntwo more transfer runs are created for `today - 1` and `today - 2`. These\ntransfer runs only affect the Performance table; other tables are not impacted.\n\nThe automatic backfills can't be disabled."]]
