|FTP/API Spec Clarification||thor.hanks||6/6/12 9:41 AM|
Wanted to get some clarification on the new Google Shopping Feed Spec.
With the new Google Shopping changes it seems like there will still be two ways to upload products to Google:
1) FTP feed upload as XML/(text/tab delimited) using the new spec (a)
2) Content API for Shopping using this spec (b)
The new spec (a) mentions the words ("If you are using XML or API..."), is this a typo? Because the new spec (a) seems to only be talking about FTP uploads.
Are the two methods above still the valid ways to send products to Google as of the new Google Shopping announcement?
|Re: FTP/API Spec Clarification||Caryn MC Guide||6/11/12 2:58 PM|
There is no change in how you upload products to Google.
|Re: FTP/API Spec Clarification||thor.hanks||6/11/12 3:41 PM|
Why does the new FTP spec mention API?
|Celebird||6/11/12 4:16 PM||<This message has been deleted.>|
|Celebird||6/11/12 4:18 PM||<This message has been deleted.>|
|Celebird||6/11/12 4:22 PM||<This message has been deleted.>|
|Celebird||6/11/12 4:50 PM||<This message has been deleted.>|
|Re: FTP/API Spec Clarification||Celebird||6/11/12 4:54 PM|
what ftp spec?
(1) there is the content-api-for-shopping requirements:
(2) there is the (new) google-shopping feed specification:
(3) a google-shopping feed may be either tab-delimited or xml formatted.
(4) a google-shopping feed may be uploaded (a) manually, (b) from a scheduled-fetch, or (c) via ftp.
in a tab-delimited formatted feed file (only) -- attribute-names
may use spaces rather than underscores and may be in the
language specified for the registered feed's target-country.
xml and the api are mentioned because -- if the data-feed-file is
xml-formatted or the content-api is used, then all attribute-names
must be in english and must use underscores, not spaces.
the above attribute-name restrictions do not change,
have been in place for quite some time, and have
nothing whatever to do with the ftp upload method --
the attribute-name restrictions relate to file format.
the data-feed-upload methods do no change.
there is the data-feed's format (xml, tab-delimited) and there are
methods to upload that data to google (manual, scheduled, ftp).
|Re: FTP/API Spec Clarification||thor.hanks||6/11/12 5:16 PM|
Yes, thank you I didn't really mean FTP only spec but instead the data-feed file based spec (manual, scheduled, ftp).
I just want to make sure that new shopping feed spec only applies to the data-feed file based (manual, scheduled, ftp) upload.
I also wanted to confirm that both the Content API and the data-feed upload methods and specs are both valid options for uploading products to Google after the new PLA changes go into effect.
|Re: FTP/API Spec Clarification||Celebird||6/11/12 5:35 PM|
first, you're welcome.
the new spec should apply to all formats and all upload methods;
the new specification is for google-shopping product-listing-ads --
regardless of format or upload method
there's been no mention of when the api libraries will be updated however.
|Re: FTP/API Spec Clarification||thor.hanks||6/11/12 5:42 PM|
So you are saying that the Content API is going to switch to using the new google shopping spec (2). Thereby changing namespacing on the elements, required/non-required fields, how fields are formatted etc?
There are many differences between the Content API spec (1) and the new Google shopping spec (2) are you saying they will be unified?
|Celebird||6/11/12 5:51 PM||<This message has been deleted.>|
|Re: FTP/API Spec Clarification||thor.hanks||6/11/12 5:54 PM|
Right no Content API changes have been announced. So as far as we know sending product through the Content API is unchanged. That is all I wanted to confirm.
However, you seem to be saying that the attribute field names from the New spec now apply to the Content API.
|Re: FTP/API Spec Clarification||Celebird||6/11/12 5:57 PM|
the namespaces should not be effected --
the reference was for the attribute-names
and the underlying rules and policies.
changes to the api with respect to google-shopping
and product-listing-ads have not been announced.
what specific differences concern you?
|Re: FTP/API Spec Clarification||thor.hanks||6/11/12 6:04 PM|
One example: featured_product
It has been a part of the Content API spec for a long time now but NOT in the old/new data-feed upload spec.
You seem to be saying that featured_product would now not be included in the content API. That sounds very fishy and wrong, with all due respect.
All I want is confirmation that the new spec is for the data-feed upload method and the Content API spec is for the Content API and that they are both valid methods of adding products.
|Re: FTP/API Spec Clarification||Celebird||6/11/12 6:42 PM|
the content-api is used for other destinations
other than product-search -- for example, to
submit price-inventory data for local-shopping.
"confirmation that the new spec is for the data-feed upload method and the Content API spec is for the Content API and that they are both valid methods of adding products." --
the content-api question specifically is probably better asked within the api group --
|Re: FTP/API Spec Clarification||Celebird||6/11/12 7:14 PM|
Why does the new FTP [data-feed file] spec mention API?
the only mention of the api in the data-feed-file spec was in the
context of underscores and english-language attribute-names.