Meta Catalog Ads: Setup, Product Sets and Retargeting Guide
Priya Raghunathan
E-commerce Performance Manager
Meta catalog ads are ads that Meta builds from your product catalogue. Instead of designing an ad for every product, you give Meta a feed of products and a pixel that reports what people view, add to cart and buy, and Meta picks which products to show each person. For any store with more than a handful of products, they are the backbone of a Meta sales account.
Quick answer: To run catalogue ads on Meta, create a catalogue with the eight required fields for every product, connect your Meta pixel so events carry content_ids that match catalogue IDs, group products into product sets, then launch a sales campaign that uses the catalogue. Use one campaign for retargeting viewers and one for broad prospecting.
This is the pillar guide for catalogue ads on Meta. If you sell clothing, our guide to catalogue ads for fashion brands covers sizes, colours and broken size runs. If you also sell on TikTok, the TikTok catalogue ads guide walks through the same steps there. For where catalogue ads sit in a full account, see our ecommerce Facebook ads strategy.
What are Meta catalog ads?
Catalogue ads on Meta are a sales ad format that pulls product images, names and prices from a catalogue and shows each person the products they are most likely to buy. Meta's Marketing API overview says they promote relevant items from your whole catalogue on any device, and it breaks the system into three parts:
- A catalogue feed that holds images, descriptions and prices.
- Pixel or app events that measure actions like views and purchases.
- Ads that show items from the feed to the audience you choose.
The format has had three names. It started as dynamic ads (often called DPA, dynamic product ads), became Advantage+ catalog ads, and Meta's current product page now says the catalogue works across all its sales campaigns rather than as one separate format. The same page reports, as of October 2026, a 17% lower incremental cost per conversion for catalogue ads compared with single-media ads. That is Meta's own figure, so treat it as a reason to test, not a promise.
Put this guide to work
Launch, test and scale campaigns on six ad platforms from one place, with Wavo, the AI copilot, at your side. Free for 14 days.
What does Meta need in your catalogue?
A catalogue is only as good as its data, and Meta rejects or hides products that miss its basic fields. Meta's catalogue fields reference lists eight fields every product needs:
id,title,description,availability,condition,price,linkandimage_link- plus at least one of
brand,gtinormpnacross the catalogue
A few fields shape how your ads behave later:
- availability:
in stockorout of stock. Meta says out of stock items "don't display at all in your ads", so a stale feed means you advertise products you cannot ship, or hide ones you can. - sale_price: must be lower than the full price. Without an end date, it stays active until you remove it.
- custom_label_0 to custom_label_4: five free text fields of up to 100 characters each. These are how you tag margin, season or bestsellers for product sets later.
- item_group_id: groups variants such as sizes and colours of one product.
- video: up to 20 video URLs per product, each up to 200 MB.
- images: JPEG or PNG, at least 500 by 500 pixels and up to 8 MB.
Most Shopify and WooCommerce stores send these fields through a partner integration or a scheduled feed URL. Whichever source you use, set the feed to refresh at least daily, because price and stock change faster than your campaigns do.
How do you connect the pixel to the catalogue?
Catalogue ads only work when Meta can match what people do on your site to the products in your feed. Meta's dynamic product audiences guide lists the website events to add: Search, ViewCategory, ViewContent, AddToCart and Purchase. Each one needs content_ids (or contents) with the same IDs you use in the catalogue.
Two details cause most matching problems:
- content_type: use
productwhen the page is one specific SKU. Useproduct_groupon a product page before the shopper picks a size or colour. Meta says AddToCart and Purchase should always useproduct. - ID format: if your feed uses the variant SKU and your pixel sends the Shopify product ID, nothing matches. Pick one ID scheme and use it in both places.
Send the same events through the Conversions API as well as the browser pixel, so ad blockers and browser limits do not thin out the signal. Then check the match rate before you launch.
How should you build product sets?
A product set is a filtered slice of your catalogue, and it is the main lever you have over which products get spend. Meta's product set overview defines it as a subset of the products in a catalogue, defined by filter rules, with filters on fields such as brand, product type and custom labels.
Useful sets for most stores:
- All in-stock products: the default for broad delivery.
- By category: so a dress buyer is not retargeted with phone cases.
- By margin: a custom label for high, medium and low margin, so you can push budget towards products that make money.
- Bestsellers and new arrivals: for prospecting with proven products, or for launches.
- Exclusions: low stock, clearance or products with high return rates.
Keep sets few and meaningful. Ten sets with three products each give Meta too little to learn from. If you want to check which products actually make a profit after ad spend, our per-SKU profit teardown shows how to find the products that quietly lose money.
Retargeting or broad: which catalogue campaign should you run?
Retargeting and broad catalogue campaigns use the same feed but do different jobs, and most stores need both running side by side. Retargeting, the classic DPA, shows people the products they viewed or added to cart. Broad delivery shows catalogue products to people who have not visited yet, and lets Meta pick both the person and the product.
| Retargeting | Broad | |
|---|---|---|
| Audience | People who viewed or carted products | People who have not engaged yet |
| Signal used | Dynamic product audiences from pixel events | Meta's delivery system plus catalogue data |
| Typical window | A few days | Not applicable |
| Main risk | Paying for sales that would happen anyway | Spending on products with weak margins |
| Exclude | Recent purchasers | Recent purchasers |
Meta's own setup example retargets people who viewed products in the last five days, excludes those who purchased in the same window, and excludes purchasers from the last ten days in its broad example. Those are examples, not rules, but they show the logic: short windows for retargeting, purchasers out of everything.
One detail matters for stores with variants. Meta applies exclusions at the product group level, so a shopper who buys any colour of a dress stops seeing that dress. Our Facebook retargeting strategy guide covers how to size windows and frequency.
Which creative options do catalogue ads have?
Catalogue creative starts from your product photos, and Meta adds several layers on top that change how each product looks in the ad. Meta's Advantage+ creative documentation lists the main options:
- Dynamic overlays: labelled "Add Dynamic Overlays" in Ads Manager, they add catalogue information such as price on top of the image.
- Template text: fields like
{{product.name}},{{product.brand}}and{{product.price}}fill your ad copy from the feed. - Catalogue video: Meta's product video guide says videos from your catalogue can show instead of images, and the option is on by default.
- Format choice: Meta can show a carousel or a collection to each person, and can generate a catalogue video as the collection cover.
- Image touch-ups: fits images to placements, with 4:5 and 9:16 on by default.
Plain white-background product shots tend to look the same as every competitor's. Lifestyle images, on-model shots and short videos in the feed give Meta more to work with. Our guide to AI product photos for ads covers ways to get those without a new shoot.
Why are your catalogue ads not delivering?
Delivery problems in catalogue ads usually come from the feed or the pixel, not from the campaign settings. Work through this list before changing bids or budgets:
- Products marked out of stock. They do not display in ads. Check that the feed updates after restocks.
- Missing required fields. Products without the eight required fields may not upload at all.
- Small or broken images. Under 500 by 500 pixels, or links that return an error.
- Rejected items. Products that fail Meta's review do not serve until fixed or re-reviewed.
- Low event match rate. Pixel
content_idsthat do not match catalogue IDs leave retargeting audiences empty. - Wrong variant images. Meta's variants guide says each variant's image and link must match its colour.
- Product sets that are too narrow. A set with five products has little room to learn.
Where Wevion fits
Catalogue ads break quietly: a feed stops refreshing, a pixel update changes the ID format, and spend drifts to products you cannot sell. Catching that early means checking diagnostics in one place, next to performance.
Wevion connects Meta, Google, TikTok, Taboola, Snapchat and Outbrain ad accounts through each platform's official API with OAuth, syncs data about every 15 minutes, and brings your Shopify or WooCommerce stores into one catalogue view, so catalogue health and campaign results sit on the same screen.
For Meta, Wevion's Product Catalogs feature shows Meta's own catalogue diagnostics and upload errors, sorted into issues to fix and opportunities. It shows how well pixel events match catalogue products on desktop, mobile and tablet. You can build product sets from 13 filter fields such as brand, price, category, availability or custom labels, create product audiences with a time window that excludes past purchasers, and target product sets per row when you bulk launch a large catalogue. Catalogue tools in Wevion work with Meta, not with Google Shopping feeds.
You can try it on your own catalogue with a 14-day trial on the Pro plan, no card needed at sign-up.
Key takeaways
- Catalogue ads on Meta, formerly dynamic ads and then an Advantage+ format, build ads from your product feed and pixel events.
- Every product needs eight required fields, and out of stock items do not display in ads.
- Pixel
content_idsmust use the same IDs as the catalogue, withproduct_grouponly on pre-selection product pages. - Product sets built on custom labels let you steer spend by margin, category or season.
- Run retargeting and broad catalogue campaigns side by side, with recent purchasers excluded from both.
- When delivery drops, check the feed, the match rate and item review before touching the campaign.
Explore more in
Campaign Scaling
Read the curated pillar page with every guide in this topic, ordered from foundations to advanced.