Fix problems with Meta feeds

Most feed problems come down to one of a few causes. Work through the ones that match what you see.

The images did not change

The data source priority is not set. In Commerce Manager, open your catalog → Data sources → Configure sources (or Settings → Data source priority). For the Image field (and Additional image link), move the OptiQube supplementary feed above your shop's own feed. Meta has no API for this step, so OptiQube cannot do it for you, and without it your shop's photo keeps winning.

The product IDs do not match. On the campaign's Feeds tab, paste your catalog's data feed URL and click Check which id matches. It counts how many of OptiQube's IDs exist in your catalog under Product ID and SKU, and offers to switch if the other one wins.

Meta has not read the feed yet. Meta reads feeds on its own schedule. Click Request update now on the data source in Commerce Manager to make it read the feed right away.

The image is not approved. Only approved creatives are in the feeds. Check the ad's Overview tab.

"no content id provided" in Meta's error report

Meta's supplementary feed import could not read the item IDs in the XML. Use the CSV URL for the supplementary feed (Copy CSV version (for Meta)). Keep the XML version for Google Merchant Center.

Products rejected in Diagnostics

Meta needs a price with a currency and a stock state for every product. Products your shop's feed leaves those out for are skipped in OptiQube's feeds as well, and the Feeds tab counts what actually goes out. Add the missing data in your shop, and the feeds pick it up on the next read.

Only one style shows

Meta allows one supplementary feed per primary feed. To run two styles side by side, give each its own catalog, fed by that style's Style feed (Full).

Still stuck?

Contact our team and include the campaign's name and a screenshot of Meta's error.