AdWords
4.9K members online now
4.9K 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 & PLAs integration with Bigcommerce SaaS

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi there,

 

I'm having a little trouble getting my Google PLAs set up with Bigcommerce ecommerce platform and am wondering if anyone can offer some advice. The problem is trying to get the feed setup so it works for multiple countries, so I can advertise in other territories other than my home (Australia).

 

I have been able to successfully set up PLAs to run in Australia, which is my store's home location, so is also the default currency, language etc (via the XML feed that is produced automatically by Bigcommerce).

 

The Bigcommerce platform can produce multiple feeds as XML files, but the problem is that Google then does not accept/approve them for it's shopping/PLAs, as the actual on-site product descriptions, IDs etc are still tied to the original store (which for me is based in Australia).

 

I have been posting in the Bigcommerce forums to see if anyone has managed to figure out a way around this, but so far no one has.

 

Bigcommerce forum post:

http://forum.bigcommerce.com/f6/google-shopping-for-multiple-countries--23835/?pid=113265#pid113265

 

 

The only information I have been able to find on the subject is this:
-----------------------------------------------

First of all, each data feed is country-specific and cannot be reused for other countries. For example if you are already advertising for the US and you want to start advertising for Germany you need a second data feed.

Secondly, the product information in the feed has to be localized (e.g. descriptions in the local language, prices in the local currency). Also product IDs need to be unique in each data feed. You cannot reuse the same IDs across multiple data feeds.

Lastly, the information in the data feed has to be 100% identical to the information on the corresponding product page.

Fulfillment of those three requirements proves to be more problematic than it seems. Many SAAS shopping carts allow prices in multiple currencies and there are also bilingual themes available, but those are all usually front-end solutions; there is no way to export those prices and descriptions from the back-end. Even if you build the feed manually or find a way to localize the product information after exporting it from the system, that would solve the problem only partially; the information in the feed will still not match the information on the product page. Why? Because the ad will redirect to the product page with a default (not localized) setting.

XXXX users can deal with this problem by creating two shops mirrored on sub domains. If you are a XXXX user and need this solution, contact XXXX sales.

In this respect self-hosted shopping carts are more reliable. Both XXXX and XXXX – the two biggest players in the self-hosted shopping cart business – do support multiple storefronts.

-----------------------------------------------

So if this is correct, is there any way to setup multiple product feeds that work with Google Shopping for multiple countries in Bigcommerce, because;
• The product IDs won't be unique for each feed (each country)
• Data has to be 100% the same in both feed and product pages

Would really appreciate if anyone has any advice to offer on this complicated subject. I will also contact Google to see if they can help.

 

Thanks in advance!

 

Guy

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by topic author Guy P
September 2015

Re: Google Shopping & PLAs integration with Bigcommerce SaaS

[ Edited ]
Top Contributor
# 2
Top Contributor


that summary basically sounds correct --
and the policies cannot be circumvented.

note that anyone from around the world may search for
any items in any of google's target-country domains --
there is nothing required and nothing that needs to
be done for that to happen.

 

the per-country policies apply only if per-country targeted advertising is

wanted -- that is, targeting ads on a specific google (shopping) domain.

also, the merchant-center does not support all countries --
a list of supported target-countries are currently here:
https://support.google.com/merchants/answer/160637

the same feed (data) cannot be used for more than one target-county --
that is not allowed and will typically result in all items being unlisted,
removed, rejected, the site disapproved or account suspended.

a new feed must be registered for each target country.

however, simply registering and creating a separate feed is not enough.

the same link landing-page usually cannot be used for more than one country --
landing-page language, price, and currency, must reflect the target-country.

the same e-commerce checkout usually cannot be used for more than one country --
the price and currency information must adhere to the policies of that country.

when registering the data-feed file for a specific target-country --
the pull-down list of countries (and the one you select) determines:
(1) which target-country rules and policies you must follow
on your site, in your feed, and for e-commerce transactions;
and (2) which google (shopping) target-country
domain your submitted feed items may be listed.

 

of course, separate shopping-campaigns are also required.

generally, yes, there are price, id, shipping, tax, delivery, customs, currency,
language, product category, payment, and product-listing-ad, requirements
per target-country -- on the website, in the feed, and for e-commerce.

typically, the website and e-commerce must first be changed to accommodate
the rules, policies, and guidelines of a target-country; then, (using the updated
website information), a different feed is created and updated to accommodate
all rules and requirements of the selected (registered) target-country to match
the website landing-page for that target-country.

yes, id values must be unique per target-country;
e.g. au-123-abc, de-123-abc, fr-123-abc

importantly, google does not allow automated machine language translation
or real-time rate-currency conversion within the data-feed or on the website.

yes, importantly, the registered target-country landing-page must be universal;
for example, if the target-country's required currency is euros then, the price
in euros (on the website's landing-page) must show exactly the same price
information regardless of where the user might be physically located --
the submitted data and link landing-page data must always match for
all users and all google's crawl requests.

if separate countries are targeted, the landing-page per target-country is
typically implemented by the url structure or separate top-level domains
or specific url parameters -- that can be properly crawled.

as to how exactly bigcommerce handles landing-pages for specific

countries with respect to a specific merchant's inventory and how

that landing-page data might be submitted, the best likely course

would be to contact bigcommerce-support directly for guidance.

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by topic author Guy P
September 2015

Re: Google Shopping & PLAs integration with Bigcommerce SaaS

[ Edited ]
Top Contributor
# 2
Top Contributor


that summary basically sounds correct --
and the policies cannot be circumvented.

note that anyone from around the world may search for
any items in any of google's target-country domains --
there is nothing required and nothing that needs to
be done for that to happen.

 

the per-country policies apply only if per-country targeted advertising is

wanted -- that is, targeting ads on a specific google (shopping) domain.

also, the merchant-center does not support all countries --
a list of supported target-countries are currently here:
https://support.google.com/merchants/answer/160637

the same feed (data) cannot be used for more than one target-county --
that is not allowed and will typically result in all items being unlisted,
removed, rejected, the site disapproved or account suspended.

a new feed must be registered for each target country.

however, simply registering and creating a separate feed is not enough.

the same link landing-page usually cannot be used for more than one country --
landing-page language, price, and currency, must reflect the target-country.

the same e-commerce checkout usually cannot be used for more than one country --
the price and currency information must adhere to the policies of that country.

when registering the data-feed file for a specific target-country --
the pull-down list of countries (and the one you select) determines:
(1) which target-country rules and policies you must follow
on your site, in your feed, and for e-commerce transactions;
and (2) which google (shopping) target-country
domain your submitted feed items may be listed.

 

of course, separate shopping-campaigns are also required.

generally, yes, there are price, id, shipping, tax, delivery, customs, currency,
language, product category, payment, and product-listing-ad, requirements
per target-country -- on the website, in the feed, and for e-commerce.

typically, the website and e-commerce must first be changed to accommodate
the rules, policies, and guidelines of a target-country; then, (using the updated
website information), a different feed is created and updated to accommodate
all rules and requirements of the selected (registered) target-country to match
the website landing-page for that target-country.

yes, id values must be unique per target-country;
e.g. au-123-abc, de-123-abc, fr-123-abc

importantly, google does not allow automated machine language translation
or real-time rate-currency conversion within the data-feed or on the website.

yes, importantly, the registered target-country landing-page must be universal;
for example, if the target-country's required currency is euros then, the price
in euros (on the website's landing-page) must show exactly the same price
information regardless of where the user might be physically located --
the submitted data and link landing-page data must always match for
all users and all google's crawl requests.

if separate countries are targeted, the landing-page per target-country is
typically implemented by the url structure or separate top-level domains
or specific url parameters -- that can be properly crawled.

as to how exactly bigcommerce handles landing-pages for specific

countries with respect to a specific merchant's inventory and how

that landing-page data might be submitted, the best likely course

would be to contact bigcommerce-support directly for guidance.

 

Re: Google Shopping & PLAs integration with Bigcommerce SaaS

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
Wow, thank you! That is an incredibly detailed and comprehensive response. I really appreciate the time it took you to write this! Smiley Very Happy