I thought we were 100% compatible if you select the option to use google you should be able to just give it the path to it. I'm double-checking into this internally with Engineering to see if that is no longer the case. I'll update you with my findings here.
Per this KB about: Feeds "It is not required to use Google data. Recommendations just uses the same format as Google. You can use this method to upload any data you have, and use the available scheduling features. However, you must retain Google's predefined attribute names when you set up the file."
Screen-shot showing where to select the google product feed from:
I don't believe that this constitutes as a correct answer.
I know how the Google Feed is setup and that it is not required to use, however, I would like to use it as a means of collecting product information outside of user driven mbox calls.
The question was:
- Does the API that ingests the Google Product feed data manipulate the incoming data to match the Target catalog data requirements. Specifically focused on the Category entity field, as the Google data structure requires semicolon delimited strings while Target requires comma delimited.
This information should be captured in documentation as anyone looking to integrate the Google Feed should run into this same question if they are concerned about their catalog.