What should you protect when Shopify market data sources change?
Protect four things separately: product identity, country targeting, operational rules and measurement history. Export the old source labels and item evidence, map every Shopify market to a country and language, copy any feed rules that will not transfer, update campaigns that filter by the old labels, and verify the live landing-page facts after the new sources appear.
Google documents that products in overlapping Shopify markets can be moved into dedicated country data sources. A new source label can make the items look new and reset the performance history shown for them, even though the underlying raw Shopify product ID remains unchanged. That distinction matters: an empty chart does not automatically mean that conversion tracking broke, and an unchanged product ID does not prove that ads, rules or country coverage survived.
This guide is for merchants using Shopify Markets with the Google & YouTube app and Merchant Center. It is not a reason to create a new feed for every country without evidence. It does not replace account-specific policy, tax, shipping or advertising review.
When does this runbook apply?
| Observed situation | Likely task | First evidence to collect |
|---|---|---|
| One Shopify market overlaps several countries | Confirm whether Merchant Center created country-specific sources and labels | Market membership, active countries, languages and delivery rates |
| Items lost their visible performance history | Distinguish a new source record from an identity or tracking failure | Old and new source labels, raw product IDs and conversion events |
| Shopping campaigns stopped serving in one country | Check whether filters still target an old source label | Campaign inventory filters and the new two-letter country label |
| Custom labels or exclusions vanished | Rebuild rules for the new source | Export of every old attribute rule and its expected output |
| Product counts increased after market expansion | Check offer count, duplicates and account quota | Country-source counts, product IDs and target-country assignments |
Do not diagnose from a single dashboard number. Preserve the object, source, country and timestamp behind it.
Build a pre-cutover evidence pack
Take the snapshot before changing Markets, the Google & YouTube app or Merchant Center data sources. If the migration has already happened, collect the same fields from logs, exports and screenshots that remain available.
- Inventory Shopify Markets. Record each market name, included countries, enabled languages, currencies, product availability, pricing adjustments and the storefront URL used for that market.
- Confirm delivery coverage. Google’s Shopify synchronization guidance says the selected countries need enabled Shopify markets and general delivery rates. Record the applicable shipping profile instead of assuming a market activation created delivery coverage.
- Export Merchant Center sources. Save the source name, label, source ID, target countries, languages, item count, last fetch or sync time and current diagnostics.
- Sample product identity. For at least the default product, a variant, an unavailable item and a discounted item, record the raw item ID, link, title, price, currency and availability.
- Save rules and campaign filters. Export attribute rules, supplemental logic, custom labels, exclusions and every campaign filter that depends on a source label.
- Save measurement context. Export the old source’s recent product performance and note the reporting window. A later reset can then be explained rather than mistaken for a sudden traffic loss.
Never put customer records, ad-account credentials, private admin URLs or API secrets into the evidence pack. Store access separately and limit the operational record to configuration and catalog facts.
Create one market-to-source map
The migration is controllable when every active country has one documented path from Shopify to the shopper. Use a table like this before release.
| Field | Example evidence | Pass condition |
|---|---|---|
| Shopify market | United States | Active and contains the intended destination country |
| Storefront URL | example.com/products/runner | Resolves to the intended market, language and currency |
| Merchant Center source | Country label US | Country and language match the storefront experience |
| Product identity | Raw Shopify item ID and variant ID | Same underlying item can be traced before and after migration |
| Commercial facts | USD 89.00, in stock | Feed, structured data, visible page and checkout agree |
| Shipping and returns | US delivery rate and applicable policy | Merchant Center settings are supported by the live site |
| Campaign scope | Filter includes source label US | Intended products are still eligible for the country campaign |
If one URL changes price or currency based only on a shopper’s IP address, test it carefully. Google’s merchant-listing guidance recommends distinct URLs for products offered in multiple currencies, and the landing page, structured data and submitted product data must agree. For variant-level conflicts, use the Shopify variant structured-data audit.
Run the after-cutover verification in order
1. Check the source inventory
List every new country source. Confirm its two-letter country label, language, item count and status. Compare that list with the Shopify Markets map; a source with no intended market or a market with no source is a release failure, not a future optimization.
2. Compare raw product identities
Use the sample set from the evidence pack. The raw product identity should remain traceable even if the source label and displayed performance history changed. If the item ID changed unexpectedly, stop and investigate before editing campaigns or combining reports.
3. Rebuild rules deliberately
Google states that attribute rules from the previous data source do not automatically transfer to newly generated country sources. Copy only rules that still match the country’s catalog, currency and policy. Test the output on a small set before applying it across every source.
4. Repair campaign filters
Campaigns filtered by an old source label can stop capturing products after the split. Add the new country label where appropriate, then verify eligible item counts. Campaigns that target all products are a different case; do not change them merely because a label exists.
5. Validate landing-page evidence
Open sampled links in a clean session. Confirm the selected market, language, price, currency, availability, shipping information and add-to-cart outcome. Then compare the initial HTML and product structured data. If price disagrees, follow the Merchant Center price-mismatch evidence workflow. If Google cannot retrieve the page, start with the product-page unavailable checklist.
6. Read diagnostics by country source
Do not aggregate away the problem. Review processing, approved, limited and not-approved states for each source. Save the exact issue, affected item count and first-observed time. A passing source in one country does not validate another country’s prices, shipping or policy.
7. Release a small sample and watch two windows
Start with representative products in one country. Verify source status and conversion events first, then expand. Keep the old and new reporting periods separate: a history reset changes the chart’s continuity, not the underlying facts you saved. Compare same-length windows only after the new source has accumulated enough data.
Common migration failures
| Failure | Why it misleads | Smallest useful repair |
|---|---|---|
| Assuming an empty performance chart means tracking failed | A new source record can reset displayed item history | Compare raw IDs and live conversion events before changing tracking |
| Keeping campaigns filtered to the old source label | Products in the new country source fall outside the filter | Map the new label and verify eligible item count |
| Expecting rules to transfer automatically | Country sources may launch without required labels or exclusions | Recreate tested rules per source |
| Activating a market without delivery evidence | The catalog targets a country the store cannot serve correctly | Configure and test the applicable delivery rate |
| Checking only Merchant Center, not the page | Feed data can still conflict with visible price, currency or availability | Compare source, initial HTML, structured data and checkout |
| Splitting every country without a management plan | Offer count, quota, rules and diagnostics multiply | Create only justified sources and assign an owner to each |
Questions merchants ask during the change
Can one Shopify store list products in multiple countries?
Yes. Shopify Markets can configure localized currency, language, product availability and pricing for countries or groups of countries, and the Google & YouTube app can sync selected countries to Merchant Center. The market, storefront, delivery and product-data settings still need to agree for each destination.
Why did item and performance history disappear?
Google documents that products moved from overlapping markets into a new country source are treated as new items in that source, so visible performance history can reset. Preserve the prior export and check the raw product identity before concluding that tracking or the product itself changed.
Do Shopify product IDs change during the migration?
Google’s current Shopify synchronization guidance says the underlying raw product IDs remain unchanged for the documented multi-market source change. Verify your own sampled IDs because apps, feed transformations or a different migration path can still alter submitted identifiers.
Do attribute rules transfer to the new sources?
No, not automatically in the documented change. Copy the rules you still need, test their output in each country source and retain a record of the old and new configurations.
Why did Shopping campaigns stop serving in some countries?
A campaign may still filter products by the old source label. Update the filter to include the new country-code label when that matches the campaign design, and confirm eligible item counts. Campaigns targeting all products are not affected by that specific filter issue.
Does every country need a separate Merchant Center data source?
Not as a universal rule. Use the source structure created or required by the integration and your actual markets. More sources increase operational work and offer count. The correct structure is the smallest one that represents country, language, currency, shipping and policy accurately.
Sources and limitations
Primary sources reviewed on September 20, 2026 include Google Merchant Center Help for syncing Shopify products, creating product data sources and product visibility and status, plus Shopify Help for getting started with Markets and assigning domains and languages. The evidence pack, mapping table and release sequence are ShopXN’s editorial synthesis.
Merchant Center interfaces, Shopify integration behavior, source labels and quotas can change. This guide does not guarantee product approval, uninterrupted ads, preserved dashboard history, indexing, ranking, rich results or Discover exposure. Validate the current official documentation and your own account before a production change.
Make every market traceable before you scale it.
A Shopify SEO audit can connect Markets, landing pages, product data and search measurement into one release record.
Discuss your Shopify setup