To run catalog ads on Meta, three pieces need to be connected to each other: a catalog in Commerce Manager, a scheduled product feed (data feed) that fills this catalog regularly, and the Meta pixel on your site sending events that match the product IDs in the catalog. The most robust setup is to build the catalog not by hand or with a one-off file upload, but so that it is fetched regularly from a fixed feed URL; that way price and stock changes are reflected in ads on their own.
This guide walks through the setup in order. Menu names in the Meta interface may change from time to time; the logic of the steps stays the same.
Understand how catalog ads work
In catalog ads (Meta's Advantage+ catalog ads) you do not prepare a separate ad for each product. Meta decides which product to show to whom, using the products in the catalog and the behavioral data coming from the pixel. That is why two things are critical:
- Catalog data must be accurate and up to date. If an out-of-stock product appears in an ad, budget is wasted and the customer has a bad experience.
- Pixel events must match the catalog. The product ID (
content_ids) sent in theViewContent,AddToCartandPurchaseevents on the site must be the same as theidin the catalog. If the match is broken, retargeting and dynamic ads work poorly.
Step 1: Create a catalog in Commerce Manager
- Open Commerce Manager in your Meta Business account and create a new catalog; choose e-commerce products as the catalog type.
- Connect the catalog to the correct business account and ad account.
- Associate the catalog with the Meta pixel on your site (or the event source coming through the Conversions API).
If you have more than one store or currency, opening a separate catalog for each makes management easier in most cases.
Step 2: Add products with a scheduled feed
There are several ways to add products to a catalog: adding them manually, a one-off file upload, a platform integration and a scheduled feed. For e-commerce stores the most controllable method is usually the scheduled feed: Meta fetches the XML or CSV URL you provide at the interval you set.
Points to watch during setup:
- The feed URL must be fixed. If the URL changes, Meta keeps fetching the old one.
- Choose the update frequency according to how fast your stock changes. If you have products that sell out quickly, schedule more frequent fetches.
- If the feed is protected, enter the username and password in the schedule settings. Meta supports feed URLs protected by credentials.
- After the first upload, be sure to read the error and warning report; products with a missing field or an invalid value are not added to the catalog.
Step 3: Fill in the required fields correctly
The basic fields Meta expects are similar to Google's: id, title, description, availability, condition, price, link, image_link and brand. The points that cause problems in practice:
- The
idfield must be permanent. If the ID changes, Meta treats it as a new product and the product's historical performance data is lost. - The price format must be consistent (amount and currency, e.g.
499.90 TRY). - For discounted products,
priceshould be the list price andsale_pricethe discounted price. - Variants should be grouped under the same
item_group_id; this way Meta recognizes the sizes of the same product as a single product family.
Step 4: Split the catalog with product sets
Creating product sets instead of running a single ad for the whole catalog lets you manage budget better. Product sets can be filtered by fields such as category, brand, price or stock. A more flexible method is to use label fields in the feed:
custom_label_0…custom_label_4: Five free-form label fields that work the same way as on Google.internal_label: A Meta-specific label field that is not shown to customers and can be used in product set filters.
For example, if you write labels such as "best seller", "low stock" or "new arrival" onto the product in the feed, you can create product sets based on these labels and run a campaign for each with a different budget and message. We explained the labeling logic in detail in the custom label strategy guide.
Step 5: Verify the sync and the matching
A few days after setup, run these checks:
- In Commerce Manager, see that feed uploads complete regularly and without errors.
- On the event sources screen, check what percentage of pixel events match the catalog. A low match rate comes from a format difference between
content_idsandid(e.g. the site sending a stock code and the feed a numeric ID). - Verify that a few products that have run out of stock appear as
out of stockin the catalog.
Meta catalog feed with HexFeed
HexFeed generates an XML feed in Meta format from the products in your store (T-Soft, Ticimax, Shopify, ikas or an XML source) and syncs product, stock and price data regularly. The feed URL is protected with a username and key; in the panel you can copy a ready-to-use feed URL for Meta with the credentials included.
You can determine which products enter the feed with rules such as stock, size availability, category, price and GA4 metrics, and write an internal label (internal_label) onto products that match the rules to use in Meta product sets. For each feed you can also choose whether variants are sent as separate rows. For setup see the Meta catalog with Shopify and Meta catalog with ikas pages; for the rule logic, see the feed filtering page.
Checklist
- The catalog is connected to the correct business and ad account.
- The catalog has been associated with the Meta pixel or event source on the site.
- Products come in through a scheduled feed from a fixed URL.
- The update frequency suits how fast stock changes.
- The
idvalues in the feed are permanent and in the same format as the pixelcontent_ids. -
priceandsale_priceare split correctly for discounted products. - Variants are grouped with
item_group_id. - A labeling strategy (custom label / internal_label) has been defined for product sets.
- The error and warning report was reviewed after the first upload.
Frequently asked questions
Platform integration or scheduled feed?
Some e-commerce platforms have a direct integration with Meta, and it may be enough for small catalogs. If you want control over product selection, labeling and images, a feed generated with rules and fetched from a fixed URL is more flexible.
What should I do if the pixel match rate is low?
First put the product ID sent in the events on the site side by side with the id value in the feed. The most common cause is one being a stock code and the other a numeric ID; or the site using the parent product ID while the feed uses the variant ID.
Should I open more than one catalog?
For a single store and a single currency, one catalog is usually enough. For different countries, currencies or brands, separate catalogs can make management easier.
When are the products in the catalog updated?
With a scheduled feed, Meta fetches your URL at the interval you set. For an update to reach the ads, both your feed and Meta's fetch schedule need to be frequent enough.
