Available for projects & agency overflow · Quick reply, from the person who does the work

Send a message contact@allaux.fr
FR EN TR
allaux.
Emergency Discuss my project

Setting up a product feed for the Meta catalogue

The Meta product feed shares much of its structure with the Google Merchant Center feed: the same core attribute names (id, title, description, link, image_link, price, availability) appear on both sides. What sets them apart is Meta’s own categorisation and a handful of fields specific to Meta Shopping and catalogue campaigns, which I prefer adapting rather than reusing the Google feed as is.

Describe my issue Send a message

The situations I handle

  • Wanting to reuse the Google Merchant Center feed directly for Meta
  • Meta catalogue imported but products poorly classified in Meta categories
  • Uncertainty over Meta Shopping-specific fields missing from a feed built for Google
  • Products rejected in the Meta catalogue manager without knowing why
  • A catalogue to prepare for catalogue advertising (Advantage+ catalog ads)

How I adapt the feed for Meta

  1. Checking the shared attributes

    I start from the attributes already present in an existing Google feed, id, title, description, link, image_link, price, availability, condition, brand, which largely carry the same names on Meta’s side.

  2. Adapting the categorisation

    I don’t reuse the Google Product Category as is: I check Meta’s own categorisation in the catalogue manager, which affects both product eligibility and catalogue ad placement.

  3. Adding fields specific to the Meta ecosystem

    I add the fields specific to Meta Shopping and catalogue campaigns (Advantage+ catalog ads) that have no direct equivalent in a feed built purely for Google.

  4. Importing into the catalogue manager

    I set up the feed source in the Meta catalogue manager and schedule regular refreshes, on the same principle as Google: a frozen catalogue eventually shows a stale price or availability.

  5. Checking rejected products

    I check the catalogue diagnostics in the Meta manager product by product, to tell an attribute issue apart from a categorisation issue before touching the whole feed.

Why not reuse the Google feed as is

The closeness between the two feeds is real: to a large extent, a well-built Google feed already provides most of what Meta expects. But deriving a Meta feed from the Google one takes adjustments, not just renaming a file.

Meta’s categorisation doesn’t follow exactly the same tree as the Google Product Category, and some fields tied to the Meta Shopping ecosystem or Advantage+ catalogue campaigns have no equivalent in a feed built purely for Google. Reusing the Google feed unadjusted risks poorly classified products or catalogue features that don’t activate correctly.

Related pages

Describe your need in one minute

A few targeted questions so I can reply with an estimate rather than another questionnaire.

outil
api
sens
frequence (facultatif)
Please provide an email or a phone number so I can get back to you.

Please provide an email or a phone number so I can get back to you.

Frequently asked questions

Can I reuse my Google Merchant Center feed as is for Meta?
Only partly. Core attributes share the same names, but Meta’s categorisation and some Meta Shopping-specific fields need checking and adjusting.
Where is the feed set up on the Meta side?
In the Meta catalogue manager, where you declare the feed source and its refresh frequency.
Do Advantage+ catalog ads need a different feed?
Not an entirely different feed, but some fields specific to those campaigns don’t exist in a feed built purely for Google and need adding.
Does a Meta catalogue also need regular refreshing?
Yes, on the same principle as a Google feed: a catalogue that stops updating eventually shows a price or availability that no longer matches the shop’s reality.

Related pages