The “Google Listings” table (YOUR CONNECTIONS > Google Merchant > Listings) in Sproxi allows you to easily search for & edit the data that appears in your data feed, with the purposes of optimizing and refining your Google Listings. In this knowledge base article we will discuss what “Processed” & “Override” values/data is & how that impacts your Google Listing. We recommend reviewing the article titled “Understanding Data Priority in Your Google Listing” to understand how the “processed” is pulled into your Google Listing and thus sent to the Google Merchant Center.
In a nutshell, a processed value is data sent out in your Google Listings Feed. An “override value” will override the value that was in the “processed value” and replace it as the new “processed value.” The override value is data you can insert directly into your Google Listing Fields, “overriding” the current value in the “processed value” field and now becomes the new “processed value.”
Navigate to the 'Google > Listings' table.
What is "Processed" & "Override" Values
A “Processed” value is the actual data Sproxi will send out as Google Listings to your Google Merchant Center account. We use the word “processed” here because when you think of the data fields in your Google Listing, this data was pulled or mapped from your shopping cart data, mapped, and/or used in a recipe in Sproxi.
A good example of a processed value is the SKU. When Sproxi pulls your WooCommerce shopping cart SKU, we use the SKU to create a product in Sproxi, and also automatically map this SKU from the WooCommerce listing to the Google Offer ID in the Google Listing. Another example may be the MPN, or “Manufacturer’s Part Number.” Using the “Field Map” tool, you can easily “map” the product’s SKU to the Google attribute field, “MPN.” This will immediately map ALL product SKUs to the Google attribute MPN. But what if there are situations where this works for most products, but there are a handful of products where the MPN does not equal the SKU. Here’s where “defined” values are helpful.
Override values is data directly written into the Google attribute field (by editing a Google Listing in Sproxi), and this will “override” any “processed” value. In layman’s terms, the “Override” value is the “King of the Hill,” and will have the highest priority in Sproxi.
How to Override a Google Listing Value
Navigate to the Google Listings table by going to YOUR CONNECTIONS > Google Merchant > Listings.
Search for the product using the search box and/or sorting the column headers. In this knowledge base article we are going to work with the Google Listing attribute “MPN.” In this scenario, the product SKU is mapped to the Google attribute MPN, but there are a few products where you will want to manually override this mapping. This process can be used for other Google attributes.
You can add or subtract columns using the “Set Columns” button. In addition, you can use the “Set Status Filters” button to filter product status:
- Visible, hidden, out of stock – product status as set in connected shopping cart
- Enabled, Disabled – products set to export (enabled) or disabled (does not export) to your Google Merchant Account, ie., product not in feed.
To help define my data & make my work a little easier, I am going to use the “Set Status Filters” button to only show “Enabled” products, meaning I only want to see products I am interested in sending to the Google Merchant Center.
By default, the “data drop-down filter is set to “Processed,” meaning the table will show the “processed” values set in the Google Listing for MPN. You can use the “Show Source Data” button, along with the “Toggle Source Legend” button to provide a visual indicator of where the “processed value” came from. We offer a detailed explanation of this in the knowledge base article titled “Using the Show Source Data Filter & Toggle Source Legend Button.”
For illustrative purposes we are showing the processed value so you can see what’s being sent in the MPN field to Google. Data shows here because we have mapped the product SKU to the Google attribute “MPN.”
In the image below, notice how the data drop-down filter has been set to “Override” (rather than “Processed”.) You will notice, in this example, there are no values showing in the MPN field. That’s because there is no data written directly into, or in “Override” value in the Google attribute value field.
For purposes of this article, I am going to write a override value into the MPN field for the product SKU “BR7-B” (the first product in the table screenshot above.”
To edit this product, I am going to click the edit icon in the actions column. This will open the Google Listing where I can edit the data. When the Google Listing opens, I am going to click the “Conditionally Required Fields” accordion tab where I can see the Google Field “MPN.”
You will notice that the “processed” value in the MPN field is “BR7-8.” This makes sense, because as we discussed above, we mapped it. However, you will also notice that there’s no value in the “Google Value” field (other than the label MPN.)
This field is empty because I have do not have data written directly into this field. For purposes of this article, I am going to write “BR7-Bronze” into the “Google Value” field and save it.
If I go back to the Google Listings table and setting the same filters, and making sure the “data” drop-down filter is set to “Defined,” will see there’s now a value appearing for this specific product.
So What Does This Mean?
What this means, is now, when Sproxi updates this product in the Google Merchant Center, the mapped MPN, BR7-B that was the processed value will NO LONGER be sent. The new value is the “Override” value which I wrote to be BR7-Broze, now becomes the new processed value.
Another way of verifying this is to take a look at the same table again, but now us “processed” in the “data source” dropdown filter. You will notice that “BR7-Bronze” has also replaced BR7-B in the “processed” table as this is what Sproxi is processing as the value in the Google attribute field, “MPN.”
This could get a bit confusing which is why we have enabled a feature called “Show Source Data.” When viewing “Processed” data, you can click the “Show Source Data” to see the source of the “Processed” value.
