FAQs about Multi-Country Google Shopping Feeds
Answers and practical guidance for setting up, localising, and troubleshooting Google Shopping feeds across multiple countries.

Image via 123RF
In This Article
Feed fundamentals
Tracking & attribution
Operational checklist
Why multi-country Google Shopping feeds matter
Running Google Shopping across multiple countries expands reach and increases revenue potential, but it adds layers of complexity: currency, language, tax, shipping, and attribution. This FAQ guide explains how multi-country Google Shopping feeds work, common pitfalls, and practical steps US-based brands and international sellers should take to keep feed data accurate and attribution clean. If you want to see how this ties into a structured growth system, explore our services overview to learn how feed strategy integrates with paid media and tracking.
How does Google decide which feed to use per country?
Google matches requests based on the Merchant Center settings (target countries and target languages) and the attributes in each feed (currency, language, availability). For multi-country setups you can use separate Merchant Center feeds per country or a single multi-country feed with country-specific attributes. Use country-specific feeds when you need distinct pricing, shipping, or tax rules.
Do I need separate Merchant Center accounts for each country?
Usually no. You can use one Merchant Center account to target multiple countries, but some large operations prefer separate accounts for clear billing and region-specific policies. For most Shopify and WooCommerce stores, one account with multiple feeds is sufficient. Learn more about account structure and strategic trade-offs on our about page.
Which attributes are mandatory for multi-country feeds?
At minimum, for each target country you must supply: id, title, description, link, image_link, availability, price (with currency), and shipping (when required). For region-specific compliance and performance, include gtin, mpn, brand, and custom_label attributes. Below is a simple attribute mapping table you can use as a checklist.
| Attribute | Why it matters |
|---|---|
| id | Unique identifier to prevent duplicates across feeds |
| price (USD / local) | Must match landing page and include currency code |
| link | Country-specific landing page or parameterised URL |
| shipping | Region-specific costs and labels |
Conversion tracking and attribution: how should I set it up?
Accurate attribution across countries requires server-side tracking and consistent parameter mappings between ad clicks and on-site conversions. Relying only on platform-reported conversions can misstate performance when cross-border redirects, currency conversions, and different checkout flows exist. For robust reporting, combine Google Ads conversion import with GA4 server-side events and a single source of truth for revenue in dollars. If your team wants a structured implementation, see how a tracking-first approach fits into a broader growth play on our homepage.
| Step | Action |
|---|---|
| Click | User clicks Shopping ad → gclid or click_id appended |
| Landing | Server-side tracking capture of click_id and session data |
| Purchase | Order recorded server-side → revenue converted to $ and sent to GA4 and Google Ads |
Funnel impact: TOF → MOF → BOF
- TOF (Top of Funnel): Market and category targeting with country-level feed reach
- MOF (Middle of Funnel): Remarketing audiences using product IDs and localized messaging
- BOF (Bottom of Funnel): Country-specific promotions, shipping options, and checkout optimisation
Advanced FAQs, troubleshooting and best practices
How should I handle currency conversion and pricing?
Provide prices in the currency of the target country when possible; otherwise annotate price with the currency code. If using automatic currency conversion, track the exchange rate used and normalise revenue to $ for cross-country reporting. For example, if a product sells for €80 and the store reports that revenue, convert to $ using the exchange rate at the time of sale for attribution consistency (note: exchange-rate values are estimates unless locked via a payment processor).
Why do I see disapproved items for some countries but not others?
Disapprovals often stem from policy mismatches: required tax or shipping attributes missing for a region, restricted items in a target country, or mismatched language/landing page content. Validate feed diagnostics in Merchant Center per country and check the item-level error messages. Use supplemental feeds or feed rules to inject country-specific attributes without rebuilding your primary feed.
Should I use one feed or multiple country-specific feeds?
Use multiple feeds when pricing, availability, or shipping differ significantly by country. A single feed can work if you standardise attributes and implement feed rules to dynamically change country-specific fields. Larger merchants typically adopt separate feeds to reduce complexity in rules and to isolate testing.
Feed debugging checklist
- Confirm currency and language match target country settings
- Verify landing pages return country-specific content and consistent price
- Ensure shipping and tax attributes exist where required
- Test product URLs with country and language parameters
- Monitor Merchant Center diagnostics for item-level errors
Practical example for a US-based Shopify merchant
A Shopify store selling apparel to the US and Canada can use two feeds: one priced in USD targeting the United States and one priced in CAD targeting Canada. Each feed should reference country-appropriate landing pages, shipping costs, and local returns policy. Server-side tracking will normalise revenue back into $ for cross-market ROAS analysis and to reduce mismatches in Google Ads reporting. If you need implementation help, talk to a tracking expert about feed-driven attribution.
Optimisation tips that improve revenue (not just clicks)
- Prioritise accurate price and shipping visibility-unexpected shipping often kills conversion
- Use supplemental feeds for promotional prices and country-level promos
- Segment campaigns by revenue-per-country and measure CAC in $ for each market
- Implement server-side event matching to reduce lost conversions from browser restrictions
Ongoing monitoring and reporting
Automate daily feed checks and include key diagnostics (disapprovals, price mismatches, landing-page errors). For cross-country performance analysis, normalise revenue to $ and report CAC and LTV by market. Prebo Digital’s approach is strategy → build → test → scale → report, which aligns feed ops with paid media and tracking. See our services overview for examples of retainer-based feed and tracking programs.
Common compliance and policy considerations
Verify product legality in target countries and ensure shipping and return terms are clearly displayed on country-specific landing pages. For US merchants expanding internationally, watch for local tax obligations and customs requirements. Merchant Center disapprovals will usually indicate the specific policy issue.

