Add CatalogBadge to your Meta catalog

This is the last step: your Meta catalog starts reading our feed, and your Facebook and Instagram catalog ads show the branded images. You work in your own Commerce Manager; we never have access to your ad account, and you do not need a new catalog.

Where to find your feed URLs

In CatalogBadge, open your store. The Overview page lists your feed URLs under Feed URLs, each with a copy button, the number of items, when it was built and when Meta last fetched it. The last step of the setup wizard shows the same URLs. Treat them like a password: anyone with the URL can read the feed.

Which feed to use

Not sure? In Commerce Manager, open Catalog, then Data sources. A data feed shows a URL and a schedule; a partner integration shows the platform’s name.

Option A: swap your data feed for ours

1. In Commerce Manager, choose your catalog and open Catalog, then Data sources.
2. Open the data feed your catalog uses now and go to its settings.
3. Replace the feed URL with your meta-full.xml URL.
4. Set the schedule to hourly, save, and choose Upload now for a first fetch straight away.

Our file carries every field of your feed unchanged apart from the images, so prices, stock, titles and product sets stay as they were. To undo, paste your old URL back. Meta’s guides: update a data feed and scheduled feed uploads.

If your catalog has no data feed yet, add one under Data sources with the same URL as a scheduled feed.

Option B: add a supplementary feed

1. In Commerce Manager, choose your catalog and open Catalog, then Data sources.
2. Open the data source your platform created and add a supplementary feed.
3. Choose a scheduled feed, paste your meta-supp.csv URL and set it to hourly.

A supplementary feed only changes the images of products your platform already sends; it cannot add products or change prices or stock. To undo, delete the supplementary feed and Meta goes back to your platform’s images on its next sync. Meta’s guide: add a supplementary feed.

What to expect on the first fetch

• Meta downloads the file, then the images. Images can take a few hours to show in Commerce Manager and in ads.
• Products whose image is not drawn yet keep their original photo in the feed, never an old image. Right after you go live, the supplementary file may have few rows or none; it fills as the images are drawn.
• Products that are out of stock, skipped by a rule or past your plan’s product count keep their original photo.

Check that it worked

1. In CatalogBadge, the feed’s line on the Overview page shows when Meta last fetched it.
2. In Commerce Manager, the data source shows its last upload and any errors.
3. Open Catalog, then Items, and open a product you expect to be branded. Its image address starts with https://img.catalogbadge.com/.

Optional: the language feed for English images

The Overview page also lists a language feed: meta-lang-en.csv for a store whose main feed is Arabic, or meta-lang-ar.csv for a store whose main feed is English. Once you add your feed in the other language and switch that language on (see your platform’s guide, for example Salla), shoppers who use Facebook or Instagram in that language see its image and title, and everyone else sees the main one, from the same catalog. Until then every row repeats your main image and title, so adding it early does no harm.

1. In Data sources, under Country and language feeds, add a new feed.
2. Choose a scheduled feed, paste the language feed URL and set it to hourly.

The file names its language in each row, so there is nothing else to set. Meta’s guide: country and language feeds.

Items still show the old image

• Meta has not fetched since the change. Meta reads our feed on the schedule you set. Check the last fetch time, choose Upload now if you need it sooner, and keep the schedule hourly.
• The new image is not drawn yet. When a price, sale or title changes, the feed shows your own photo until the new image exists, on purpose: an old image could show an old price. It switches on the next fetch after the image is ready.
• The product is not branded on purpose. Out of stock, skipped by a rule, past your plan’s count, or a photo we could not load. Your store’s dashboard says which.
• Supplementary feed ids do not match. If the ids in your source feed are not the ids your platform gives the products in Meta, Meta ignores those rows.

Each image address changes only when the image itself changes, and Meta re-downloads an image only when its address changes, so an unchanged product keeps its image. More in images and updates and timing. Still stuck? Write to hello@catalogbadge.com.