Customize Google and Facebook formats to their current specifications

Lukáš Horák
1. 9. 2020
2 minutes read
Customize Google and Facebook formats to their current specifications

Google and Facebook have added new elements to their specifications in recent months without any notification. As a result, in Mergado, these elements were not automatically hidden in projects that had the Google or Facebook format on input.

Google and Facebook have added new elements to their specifications in recent months without any notification. As a result, in Mergado, these elements were not automatically hidden in projects that had the Google or Facebook format on input. Although we’ll include adjustments to these formats in the next release, we want to let you know what to keep an eye on.

What new elements have Google and Facebook added

What effect does this have on your projects in Mergado

Many output formats (e. g. Heureka) automatically hide the given elements when converting from Mergado to export XML.

HOWEVER:

Other formats (e. g. MallMarketplace, Árukereső) cannot automatically hide these elements when creating XML, but allow them to be hidden manually on the Elements page. If the user does not hide them manually, they are transferred to the output XML. Facebook and Google format elements start with the so-called “G:” namespace and this fact must be defined in the XML header. If this is not the case, the XML will start to contain elements that the commodity does not support and render the format invalid.

Our modification in the release on September 2, 2020, will cause these elements to be hidden, not output, and the XML will remain valid. If you may be using these elements, be prepared to be hidden in early September 2020.

What Mergado can convert from advanced elements

Facebook translates new elements:

  • G:INVENTORY -> storageqty (MergadoXml)
  • G:GENDER -> gender
  • G:SIZE -> size
  • G:MATERIAL -> material
  • G:MOBILE LINK -> url_mobile
  • G:COLOR -> color

In Mergado, we can upload and convert parameters through it. And so that:

we convert to G:ADDITIONAL_VARIANT_ATTRIBUTE|Style, Cool.

IMPORTANT

We only convert parameters from Facebook to other formats. Conversely, we cannot convert to G: ADDITIONAL_VARIANT_ATTRIBUTE — Facebook does not want this element to contain the main attributes (color, material, etc.), but only additional ones.

Google converts the new G: TAX | G: RATE element to -> vat. Newly also supports parameters where from:

it creates G: ATTRIBUTE_VALUE | Product Type, Digital player.

If the format supports these parameters, it can easily convert them. For Google, this works the other way around.

Did you know that Mergado helps you correctly map categories for both Google and Facebook? Find out how on our blog.

Do you have any questions or need help with setup? Do not hesitate to contact our technical support.

Read more:

Lukáš Horák

Lukáš takes care of most of the Czech and English communication in Mergado. Through blogs, e‑mail, and social networks, he regularly supplies readers with e‑commerce news and news and tips from Mergado. In his time off, he enjoys simple things like badminton, digging the hidden gems of the 80’s, and seafood served with red wine.