Meta catalogue without manual work: a fixed feed and a delivery report
Catalogue ads pick products from the feed. When a product has an error, is out of stock or dropped out of the feed, Meta will not show it and you do not know why. Basketly repairs the feed before Meta, and the Meta catalogue delivery report points to products without impressions and the most likely reason.
The demo has sample data; the login comes to your e-mail.
Feed: the same source, a clean result
You open Feeds and take a feed from a shop, an address or a file, or the products of a shop connected through its API. Basketly repairs the products, applies the rules and serves the result at a secret address that you paste into Commerce Manager. A feed for Google Merchant Center works the same way, so you can copy one feed and give the other channel its own rules. You change the feed once, and Meta fetches the new version at its next read.
Format and fields that matter for the catalogue
The Google / Meta format is Google Merchant RSS 2.0. CSV has one column per attribute, in Google’s names. The Ceneo format is not read by Meta, and neither is the CSV for ChatGPT. The product id in the feed must match the id in purchases, because Meta ties a purchase to a product by it. That is why fixes and rules never change the id.
Meta catalogue in 4 steps
It takes a few minutes if the Meta ad account is already connected.
Add a feed
In Basketly open Feeds and add a new feed from an address, a file or a connected shop. Keep the Automatic fixes on.
Choose the Google / Meta format
In the Output feed tab keep the Google / Meta format (or CSV) and copy the feed address.
Paste the address in Commerce Manager
In Meta’s Commerce Manager add this address as the catalogue’s data source. The feed page has a link straight there.
Check delivery
In Reports open the Meta catalogue delivery tab and go through “Not shown” and “Sold out but shown”. Start with the reasons you can fix with a rule.
Catalogue delivery: why a product is not shown
The report sets products that could have been shown against those that were. The level of knowledge is named: “In the Basketly feed” (the product reaches the output of a feed Meta can read) or, weaker, “Probably in the catalogue” (when no such feed exists). For a product without impressions in the period, the first matching reason from the list is:
- outside the feed, or excluded by a rule (with the rule and feed named),
- out of stock, or a Meta catalogue error (with the check named),
- freshly added (in the catalogue under 2 days),
- Meta does not pick it: the product passes every check Basketly sees.
Products sold out but still in ads
The second tab shows products that went out of stock yet still have impressions, and how much was spent on them in that time. It also shows products back in stock at least 3 days ago that have had no impressions since. The panel suggests an “exclude out of stock” rule, and the page states that dates are a comparison, not proof of a cause.
Where the report gets impressions
From reading the ads of the ad account you chose when connecting. Product impressions are read per ad and day (28 days on the first read, then the last 3 days, at most every 6 hours). Meta gives no conversions per product, so the report speaks about delivery, not sales from an ad.
What it does not do
- It does not add the feed to Commerce Manager for you: you paste the address yourself.
- The reason “Meta does not pick it” is not an explanation of Meta’s decision, only a note that Basketly sees no error. The report does not settle why Meta’s algorithm does not show a product.
- Without purchases from the server and the ads report there is no link between a catalogue product and sales: Meta gives no conversions per product.
- Meta accepting a feed does not prove campaign optimisation or that an ad gets the credit for a purchase.
- The Ceneo format and the CSV for ChatGPT are not read by Meta.
Google RSS 2.0 or CSV with Google column names. The Ceneo format and the CSV for ChatGPT are for other channels.
The Meta catalogue delivery report gives one, the first matching reason: outside the feed, excluded by a rule, out of stock, a catalogue error, freshly added or “Meta does not pick it”. With a connected Meta catalogue, reasons from Meta itself are added.
Yes, with the “exclude out of stock” rule the panel suggests from the “Sold out but shown” report. The product leaves the feed at Meta’s next fetch.
Yes. Meta ties a purchase to a product by its id, so the one in the purchase must equal the one in the feed. Basketly never changes it in fixes or rules.
The feed does. The Meta catalogue delivery report needs the ads read from the ad account chosen when connecting.
See also
- Product feedsYour shop’s feed fixed automatically and by your rules, every product diagnosed against Google Merchant Center and Meta catalogue requirements, served at its own address.Read
- Product statisticsImpressions, clicks and spend of every product in Meta catalogue ads, next to views, carts and sales in your shop.Read
- Google Merchant CenterA feed from a shop, address or file, repaired and ready to paste into Merchant Center.Read
- Products Meta barely shows in catalogue ads: how to find them and give them a chanceHow to see which products Meta barely shows in catalogue ads, read impressions, product views and sales side by side, and turn them into a separate feed.Read
- Product data guidelines of Google, Meta, TikTok and Pinterest: rules with sources and AI titlesProduct data rules of Google Merchant Center, the Meta catalogue, TikTok and Pinterest: how to see which ones your products break and how title suggestions work.Read
Get started in under 5 minutes
Connect your shop and Meta and see how many purchases really arrive.
- Free up to 100 orders a month
- No developer needed
- Purchase balance and self-check