The “Field Map” in Sproxi is a powerful tool that allows you to map data in Sproxi to Google attribute field.  Sproxi takes a different approach to field maps in that within each map you create separate “mappings” for Google attribute fields.  Once created, Sproxi will begin searching for the mapped data and applying it to the selected Google attribute field in your Google listings.

Most feed creation platforms will have one large mapping feature where you select one data source for each Google attribute.  For example, most platforms will allow to you select on field as the “source” data that you then “map” to one Google attribute.  This sometimes limits the benefit of mappings because often times you have to pull data from different sources to satisfy a Google attribute field.

Field maps are prioritized from top to bottom. When processing values, Sproxi will check each map until it finds a value that is not empty. You may drag and drop the rows to change priority.

For example, let’s say you sell T-Shirts in your WooCommerce store.  To create T-Shirt variations in your store you use the size attributes of Small (S), Medium (M), and Large (L).   Since color is a requirement for apparel in Google Shopping, you need a way to get “Color” into your Google feed.  Maybe you can map an attribute named “color” from your store to the Google attribute field “Color.”

If you’re very familiar with WooCommerce you understand that you cannot “attach” an attribute to a variation unless that attribute is used to actually create the variation (like size mentioned above). 

Now you’re back to the question, “how do I get colors for my T-Shirts” into my Google feed.

Sproxi offers many different ways to do this.  One could be to create a custom field called “Color” in Sproxi and the assign that custom field, with a specific color to your T-Shirts in Sproxi.  You would then create a map in Sproxi that maps the custom field “color” the the Google attribute field “color.”  But if you have thousands of T-Shirts, this may be hard to do.

But knowing you have the specific T-Shirt color mentioned in the variation description, you could create different maps to search out these colors and map them in the Sproxi Field Map tool.

Navigating to the Sproxi Field Map Tool

To navigate to the field map too, go to “CONNECTIONS > Google > Field Map” in the left-hand navigation.


After clicking the “Field Map” navigation on the left, click the associated “Go To Field Map” button in blue.


In this example, there is one Field Map showing for one merchant id.  If you are creating & managing multiple Google Shopping feeds you will see multiple accounts in this table.  Go to the field map that corresponds to the specific feed you are working on.

Next, click the green “Create New Map” button.  You will notice on the screenshot below there are several entries showing.  Each of these are what we call “Maps” in Sproxi.

Each “Map” within a “Field Map” is some data in Sproxi mapped to a Google attribute field.

In this example you will notice a “Map Type” named “Product Search & Add Content Map.”  This simply means the source of data in this example will be Sproxi products (imported from your shopping cart).

“Map From” is the actual procedure this map will follow.  Here Sproxi is searching in the product description for the word “blue” and placing content, the word “Blue” in the Google attribute field “color.”

In the second entry we created another map that will also search the Sproxi product description for the words “baby blue” and add the content “Blue” in the Google attribute field “color.”

Once these mappings are saved, Sproxi will begin the process of cycling through each mapping, from the bottom up, trying to satisfy the mappings I created.  As it searches through products, if it finds the words “baby blue” in a description it will add the word “Blue” to the Google attribute field “color.”  If a product does not have the word “baby blue” in it, it will not insert anything, and look to rule above it.

IMPORTANT: You can have multiple field maps and Sproxi will give the highest priority to the top listed field map.  Ultimately, if you have two field maps that target the same Google attribute field, the highest ranked field map will override a lower one.  Do not confuse this with the fact that if Sproxi cannot find the Sproxi field to populate the Google attribute with, it will skip that listing and insert nothing.



How to Create a New Map

The video below illustrates how we created the individual mappings you see above.  We are using the specific mapping type of “Search & Add Content” but the process is similar for all mapping types.


"Map From Data"

“Map From Data”is the data source within Sproxi where you are pulling data from. 

The list below highlights currently available data types available to map from.

  • Attributes:  Attributes imported from your shopping cart.  Examples of this data are colors, size, or any other attribute created in your shop.  You can also create your own attributes by navigating to “PRODUCT MANAGEMENT > Tools > Attributes.” 
  • Custom Fields:  these are custom fields you created in Sproxi found by navigating to “PRODUCT MANAGEMENT > Other > Custom Fields.”  Once custom fields are created they will appear here.  To create custom fields, please reference the knowledge base article,  “How to Create & Apply Custom Fields in Sproxi.
  • Meta Data:  this is data imported from your shopping cart usually created by plugins, themes, etc.  For example, if you created custom fields in your WooCommerce store using the plugin “Advanced Custom Fields,” it will import into Sproxi as meta data.  For additional information on how this data is handled in Sproxi, please see this knowledge base article on Meta Data in Sproxi.
  • Recipes – Recipes are formulas you can create that contains a combination of static values and or dynamic values.  For detailed information on recipes, read the KB article, What Are Recipes in Sproxi?
  • Product Fields
  • Tags
  • Search & Add Content or Replace – various different tools to replace, match, or add content.  See KB article,