Oops! This email does not have permission to open a ticket. Please contact responsible for your store to provide access.

Google Shopping - FAQ Internal (construction)

THIS IS A FAQ FOR INTERNAL USE ONLY.

This guide is intended to indicate solutions to problems that may arise in Google Shopping Integration. This article is divided into 3 sections: "Questions", "Ads/Products" and "Settings"

NOTE: If you can't find your answer below and need to open a call with the Connections team, you must ask the customer to provide access to their Google Merchant account to the the following emails:

GOOGLE SHOPPING TRAINING

Have you watched our training? Here we show the integration setup, authentication, common errors and it's possible causes.
https://vtex.slack.com/archives/C928RF5PC/p1609936369293200  

 

DIAGRAM | PRODUCT INTEGRATION FLOW IN GOOGLE SHOPPING

mceclip0.png

QUESTIONS | PRODUCTS


Q:
What can cause price/stock divergence in Google Shopping?
A: Before starting an analysis, check if the seller uses Native integration (API) or XML, in the case of a Native integration the investigation follows with Connections team, if it's XML it must be verified with the Merch team. Considering these points, we recommend reviewing the following settings:

[VTEX Configuration]

Step 1. Check if the account is authenticated;
Step 2. Check if the endpoint has been correctly configured for the Google Shopping affiliate;
Step 3. Check the configurations running a checkout simulation , using a sample sku 
Step 4.  Check if the product is linked to the Trade Policy of Google Shopping
Step 5. Check if the SKU has a fixed price registered
(fixed price context following the FAQ)


[Splunk]

Step 1. Check if the broadcaster is receiving notification for price/stock change:
index=ccnotificator account=test 2148137


Step 2. Check the log if the price/stock is being sent correctly to the marketplace:
index=sellercenterintegration account=teste 


[Merchant Center Setup]
Step 1. Ask the seller for access to the Merchant Center;
Step 2. Automatic Improvements > Enable automatic updating of items > We recommend that the seller keep this switch turned off, as the integration already updates for price/stock, it's not necessary to enable. When enabled in a native integration it can cause conflict and divergence in price.
Step 3. What value is being written in the field "Raw feed attributes: account API"? This field within the Merchant Center is the most important, this is where the seller can validate what the integration is sending to google.

[Crawler google]
After that, who is responsible for updating the information is the google crawler, which visits all the product pages. When the crawler cannot see the price correctly, there is probably an error related to the structure of the page.

This google tool can help investigate errors related to page structure: https://search.google.com/test/rich-results?id=ajJ9-HfCwo7rJUd13N1glg 

[Important]
As an integration, we do not have control of the structure and customizations of the product pages, but there is some documentation that can guide the agency/seller:

Configuring discounts for orders prepaid in full on Google Shopping:
https://help.vtex.com/en/tutorial/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping--40K3R5d4NogMvCzIWdWt3e 

Using Checkout API to set a discount:
https://developers.vtex.com/vtex-rest-api/docs/using-checkout-api-to-set-a-discount 

[Understanding Price Update Flow - Non VTEX Seller Products]

Q: I would like to better understand the price update flow in Google Shopping integration for non-VTEX seller products that use EXTERNAL HUB  for catalog integration with VTEX.
A: When the Marketplace is external, the flow must be seen with #team-marketplace. All external sellers need to notify the marketplace when the price changes, and this needs to be enough for the marketplace's own flows to update their data where necessary (like other external integrations). To confirm if the connector is updating correctly, it's possible to force a notification, if the broadcaster is notified then the connector is ok.

[Notification - Price]

http://{{AccountName}}.vtexcommercestable.com.br/api/notificator/changenotification/{{Idsku}}/price 


[Notification - Inventory]

http://{{accountName}}.vtexcommercestable.com.br/api/notificator/changenotification/{{Idsku}}/stock 


[Notification - Product]

http://{{AccountName}}.vtexcommercestable.com.br/api/notificator/changenotification/{{Idsku}}  


Q:
Why some skus show a diference of -5% in the Merchant Center over the value registered in the VTEX Catalog? 
A: In these cases, check if the key "Consider discount for payment with Boleto ( Bank Slip ) on the price sent (Discount in cash)" is enabled. If so, the seller has enabled the payment method by bank slip, that is, the price of the product sent to Google Shopping will be the value with this discount. The integration will send the sku price considering the discount. (The key is inside the GS integration setup card).

 

Q: Will Google Shopping products without update expire in 30 days ? 
A: Yes, no action is required from the seller . A system is in place that control this and sends Google an update every 30 days. 

 

Q: How is the item_group_id attribute filled in the XML native integration ? 
A: Here is how it works: ItemGroupId = sku.ProductId, this means that it will look and grab the  ProductId.


Q: Is it possible to somehow configure the item_group_id in the XML native integration ?
A:No, because it gets this information from a Get in the product inserted in the GoogleShopping

 

Q: Is it possible to send customlabels to Google Shopping using the Native Integration? 
A: Yes, it is possible to manage custom tags in VTEX Google Merchant Connector.
If the product has a specification field, the connection will send it. 
As you can see below, the fields marked with  (*) in Google , are custom.

 

mceclip0.png

Q: How does the integration of the promotional price works ?

A: The integration sends the price defined in the commercial policy linked to Google Shopping". If there is an offer price (From/By), only the "Per" price will be sent.

If there is a cash discount promotion (promotion subject to the BOLETO payment method), this benefit will be applied to the value of the product before shipment. If this boleto discount flag is enabled on the configuration card.

 

Q: How does the "Do not send EAN (GTIN)" flag work?

A: When the client sets this flag in the configuration card, the skus are sent to Google with the field “gtin”= null in the Json. But there is a rule in Google shopping about submitting some properties. When we don't send the "Gtin" ,in the case Gtin=null, Google requires the "mpn" field to be filled (mpn is the manufacturer's code).

If the mpn is not filled in in VTEX, the integration also sends this field as “null”.

These products appear on Google Merchant with an alert when we send them like this, but this does not invalidate the product and they can be be sold normally, however performance can be degraded.

Additional documentation: https://support.google.com/merchants/answer/6324482?hl=pt-BR

 

Q: When does the integration update the product feed?

A: The integration will update in two situations:

  • Initial update. (When the merchant sets up the integration.)
  • Whenever there is a change in the catalog. (SKU, price and stock.)

 

Q: How does the SKU updating flow work?

A: Sku reindex > Sku enters a queue (this queue is shared with all other accounts) > Skus will be reprocessed based on the queue  order > If the Sku has an error in reprocessing, or it is re-queued or discarded > It goes back to the end of the queue.

 

Q: Is it possible to change image of an already integrated sku successfully?

A: Yes, the integration is notified whenever the sku is updated (re-indexed)

 

Q: What is the average time to update a sku on GS?

A: It is hard to predict as it will depend a on the queue size > It is necessary to analyze the log + data and understand if this sku went back to the end of the queue (because it received an error or was reprocessed). Please remember that if the Sku displays an error in the processing, it is either re-queued (going to the end of the queue) or discarded. Query to analyze log: index=gsintegration account= {{idsku}} 

INVESTIGATIONS | PRODUCTS

 

Scenario: "Sku does not integrate with Google Shopping."
How to investigate:
First step, do a checkout simulation using Postman. Here you can understand what is the situation of the sku in the moment of the integration.
In the example below, the checkout showed us an error: " A communication error with the Catalog occurred - Accessed denied to the seller 1 Neste exemplo checkout retornou erro: "Ocorreu um erro de comunicação com o Catálogo -  Seller 1 does not have authorized access to the sales channel 26".

 

 

 

 



Have more questions? Submit a request

Comments