AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
2.3K members online now
2.3K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Google Shopping multi language feed with Google Sheets

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Dear Community,

 

I am struggling to find a guide to set up a multi language and multi currency feed in Google Shopping via google sheet.

 

 


The only way I found is to create multiple feeds assigning different item IDs to the same product in different languages, but this of course is not a good solution.

 

Any smart idea/guide on how to do it in a scalable and clean way Smiley Happy?

 


Thank you a lot and best,

Roberto

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
October

Re: Google Shopping multi language feed with Google Sheets

[ Edited ]
Top Contributor
# 2
Top Contributor

generally, there are no shortcuts with respect to the policies.

if the target-country differs by both language and currency, then
google allows only two options with respect to shopping-ads --


either, (a) separate primary-feeds per target-country:

use fixed-prices and human-translated content with separate landing-pages,
per target-country -- register a separate primary-feed per target-country,
and then submit a separate primary-feed, per target-country, that matches
the landing-page details exactly -- multiple feeds per target-country are
required, but google dropped the different-id-per-country requirement.

 

create the landing-page, first, for each target-country,

per google's rules and policies for that target-country;

then, create a separate feed (spreadsheet), per country,

that matches the landing-page details, exactly.

to stay within the rules and policies, typical implementations include using
url-parameters with server-side-scripts and server-side-scripting-language, or
separate directories/folders -- for each supported currency country/language;
e.g.
http://www.example.com/products/widget?locale=us-en&color=red&size=large
http://www.example.com/products/widget?locale=ca-fr&color=rouge&size=grand

http://www.example.com/products/widget?locale=de-de&color=roter&size=grober
or
http://www.example.com/products/widget-red-large
http://www.example.com/ca-fr/products/widget-rouge-grand

http://www.example.com/de-de/products/widget-roter-grober

or, (b) one primary-feed with separate supplemental-feeds per target-country:

the same landing-page is used for all target-countries.

google's multi-country-feed (automated currency-conversion) feature
is used and a multi-country-feed must be added, per supported country,
under the primary-feed, using the primary-feed's target-country settings --
google handles the currency-conversion automatically.

then, a supplemental-feed must be created and submitted,
per-target-country -- that contains the human-translation
of the primary-feed-data (title, description, etc.) and
optionally any shipping or related per-country details.

each supplemental-feed will be automatically added as a feed-rule.

note that there is no real data in a multi-country (currency-conversion) feed;
rather, the data is generated automatically, by google, from a combination
of the primary-feed data, the automated currency-conversion by google, and
the supplemental-feed/feed-rule containing the human-language-translation
of the primary-feed data.

this method tends to have limited performance over time --
since the shopping-ad (price, currency, and language) shown
for other target-countries will not match the landing-page.

importantly, regardless of which option is chosen -- the landing-page details
must be identical for all users, regardless of where the user is physically
located and regardless of user-specific details, such as browser, user-agent,
device, ip-address, etc.

 

e-commerce systems that support multiple countries

and google-shopping-ads may be able to automate

some or most of the details in a scalable and clean

way -- but the human-language translation and any

fixed-price accounting, usually require some care.

 

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
October

Re: Google Shopping multi language feed with Google Sheets

[ Edited ]
Top Contributor
# 2
Top Contributor

generally, there are no shortcuts with respect to the policies.

if the target-country differs by both language and currency, then
google allows only two options with respect to shopping-ads --


either, (a) separate primary-feeds per target-country:

use fixed-prices and human-translated content with separate landing-pages,
per target-country -- register a separate primary-feed per target-country,
and then submit a separate primary-feed, per target-country, that matches
the landing-page details exactly -- multiple feeds per target-country are
required, but google dropped the different-id-per-country requirement.

 

create the landing-page, first, for each target-country,

per google's rules and policies for that target-country;

then, create a separate feed (spreadsheet), per country,

that matches the landing-page details, exactly.

to stay within the rules and policies, typical implementations include using
url-parameters with server-side-scripts and server-side-scripting-language, or
separate directories/folders -- for each supported currency country/language;
e.g.
http://www.example.com/products/widget?locale=us-en&color=red&size=large
http://www.example.com/products/widget?locale=ca-fr&color=rouge&size=grand

http://www.example.com/products/widget?locale=de-de&color=roter&size=grober
or
http://www.example.com/products/widget-red-large
http://www.example.com/ca-fr/products/widget-rouge-grand

http://www.example.com/de-de/products/widget-roter-grober

or, (b) one primary-feed with separate supplemental-feeds per target-country:

the same landing-page is used for all target-countries.

google's multi-country-feed (automated currency-conversion) feature
is used and a multi-country-feed must be added, per supported country,
under the primary-feed, using the primary-feed's target-country settings --
google handles the currency-conversion automatically.

then, a supplemental-feed must be created and submitted,
per-target-country -- that contains the human-translation
of the primary-feed-data (title, description, etc.) and
optionally any shipping or related per-country details.

each supplemental-feed will be automatically added as a feed-rule.

note that there is no real data in a multi-country (currency-conversion) feed;
rather, the data is generated automatically, by google, from a combination
of the primary-feed data, the automated currency-conversion by google, and
the supplemental-feed/feed-rule containing the human-language-translation
of the primary-feed data.

this method tends to have limited performance over time --
since the shopping-ad (price, currency, and language) shown
for other target-countries will not match the landing-page.

importantly, regardless of which option is chosen -- the landing-page details
must be identical for all users, regardless of where the user is physically
located and regardless of user-specific details, such as browser, user-agent,
device, ip-address, etc.

 

e-commerce systems that support multiple countries

and google-shopping-ads may be able to automate

some or most of the details in a scalable and clean

way -- but the human-language translation and any

fixed-price accounting, usually require some care.