The catalog: one feed, many surfaces
A catalog in Commerce Manager is a structured list of the items a business sells, each with an identifier, title, description, image, price, availability, link and the optional attributes that make filtering and matching possible. Meta documents several ways to fill it: a data feed file uploaded once or fetched on a schedule, pixel-based updates from the product pages' structured data, a direct integration from an e-commerce platform, and an API for stores that need near-real-time changes. The catalog is then referenced by whatever needs product data rather than copied into it, so a price change in the feed propagates to every ad and shop listing that shows the item.
That design has one requirement that catches most retailers at least once. The product identifier in the catalog must match the identifier the pixel and Conversions API send when someone views, adds or buys an item. Catalog ads for people who viewed a product work by joining those two streams; if the site sends one set of IDs and the feed holds another, the ads cannot know what anyone looked at and RemarketingAdvertising to previous visitors or engagers. from the catalog degrades to generic prospecting. The same join is what lets reporting attribute revenue to specific products.
Setting up a catalog and keeping it healthy
Setup is a one-time job; health is continuous. The feed should carry every attribute Meta's specification treats as required, plus the optional ones that improve matching and let you build product sets: brand, category, condition, colour, size, custom labels for margin tiers or seasonal groups, and sale price with its effective dates. Titles should name the product the way a customer would, with the brand and the distinguishing attribute, because the title is the ad headline. Images need to meet the format rules and should show the product cleanly; lifestyle images belong in the ad creative, not the feed. The same discipline that produces a good Merchant Center feed for Google Shopping produces a good Meta catalog, and many stores run one source for both with platform-specific mappings.
Health means three routines. Sync frequency should match how often prices and stock change on the site, so that an ad never shows a price the landing page contradicts; Meta flags mismatches it detects and can disapprove items. The diagnostics view in Commerce Manager lists item-level errors and warnings, and someone should own clearing them weekly. Product sets, the filtered subsets of the catalog that ad sets and shop collections point at, should be reviewed whenever the range changes so that a "new in" set is actually new and an "in stock" set excludes what sold out. The site's own product pages, covered in the e-commerce SEO hub, are the source of truth the feed must mirror.
The commerce surfaces
One catalog feeds several places where products appear. Meta's documentation groups them under commerce, and they differ in who initiates the view and how much the advertiser controls.
| Surface | What it shows | Who sees it | Advertiser controls |
|---|---|---|---|
| Advantage+ catalog ads | Products assembled per person from the catalog, in carousel, collection or single-image formats | People in a retargeting pool or a broad audience the system selects | Product set, template, creative overlays, audience and optimisation event |
| Shops on Facebook and Instagram | A storefront with collections, checkout on site or on Meta where available | Visitors to the Page or profile, people who tap a product tag | Collections, layout, which items are visible |
| Product tags in organic posts and Reels | A tappable tag linking a post to a catalog item | Followers and people reached organically | Which products are tagged on which posts |
| Collection and Instant Experience ads | A hero creative over a grid of catalog products | Whoever the ad set targets | Hero asset, product set order, destination |
| Catalog items in Advantage+ sales campaigns | The system draws on the catalog alongside standard creative when a catalog is attached | Audiences the automated campaign selects | Catalog and product set, creative, budget |
The naming of Meta's automated sales campaign setups has changed over time, so check the current Ads Manager labels rather than relying on older guides; the mechanism, a catalog attached to a campaign that the system fills, has stayed the same.
The guide
This hub has one in-depth guide, Advantage+ catalog ads, which covers the ad type most retailers mean when they talk about product ads on Meta. It explains how the retargeting mode reconstructs a person's browsing from pixel and Conversions API events, how the broad mode uses the catalog for prospecting without a viewing history, how product sets segment the catalog by margin or season, which formats the ads can take and how to layer creative over the product image, and how to read the breakdowns that show which products and sets are carrying the revenue. It also sets out the setup order, from event matching through the first retargeting ad set to a prospecting ad set that runs alongside it.
The guide does not cover feed construction in detail, because the feed specification is Meta's and changes; it points to the documentation for required attributes and spends its words on what to do with a working catalog. Audience sources for the retargeting pools, including how long a viewing window should be and how to exclude recent buyers, are the targeting hub's subject, and the two should be read together.
Measuring product ads
Product ads are measured in money, which makes them both easier and more dangerous to judge than lead campaigns. The platform reports purchases and purchase value attributed within the chosen attribution window, and from those a return on ad spend (ROASRevenue generated per unit of ad spend.) per ad set, product set and product. Three questions decide whether that number means anything. Is the purchase event carrying value and currency correctly, and is it deduplicated between pixel and Conversions API so revenue is not counted twice? Does the attribution setting match how the business thinks about credit, given that retargeting ad sets by design reach people who were already close to buying? And is the figure compared against a break-even calculated from margin, which the ROAS calculator does, rather than against a round number?
Average order value (AOVAverage revenue per order.) is the second product-ad metric worth watching, because catalog prospecting often shifts the mix of products sold, and a campaign that lowers cost per purchase (CPACost of each conversion.) while halving the basket is not a win. The measurement hub covers event setup, deduplication and attribution settings in depth.
A homeware store's catalog ads after an ID mismatch
A homeware store with 1,400 products runs catalog retargeting at £60 a day and sees a ROAS of 1.9, below its break-even of 2.6. Diagnostics show no feed errors, but a check of the pixel events reveals the site sends content IDs with a "SKU-" prefix that the feed omits, so only about 15% of viewed products match and the ads fall back to bestsellers. After the developer aligns the IDs, match rate rises above 90% and the same ad set reports a ROAS of 4.3 in the following month at an average order value of £84, up from £71, because people now see the specific items they had been considering. The team then adds a prospecting ad set using the same catalog at £40 a day, which returns 2.9 on its own.
Common commerce problems
Commerce issues usually surface as a reporting oddity before anyone looks at the catalog. The table maps the symptom to where the explanation lives.
| Symptom | Likely cause | Where to look |
|---|---|---|
| Catalog ads showing bestsellers to everyone, not what people viewed | Product IDs in events do not match the catalog | Catalog ads guide |
| Items disapproved or missing from ads | Feed errors, price mismatches with the landing page, policy issues | Commerce Manager diagnostics; the feed source |
| ROAS high on retargeting, low overall | Retargeting is taking credit for near-certain purchases | Measurement hub |
| Revenue double-counted | Pixel and Conversions API purchase events not deduplicated | Measurement hub |
| Recent buyers keep seeing ads for what they bought | Purchaser exclusion missing, a purchase event that does not match the catalog, or a cross-sell set that includes the item | Retargeting ads reaching recent buyers |
| Shop shows wrong prices after a sale | Sync schedule slower than the site's price changes | The feed's fetch schedule |
| Specific catalog items never appear in catalog ads | Diagnostics errors, product set rules, content ID mismatch, stock or a stale feed | Diagnosing catalog products not showing in ads |
The Meta Ads expertise page describes how the author runs catalog-led accounts and the retailer types that experience covers; this hub explains the machinery.
