Skip to content

Meta Advantage+ catalog ads: what they are and what you need first

Account operationsUpdated 14 Nov 20265 min read

Cover: a spreadsheet turning into product cards and then a carousel ad on a phone
In this article
  1. What you need before creating a campaign
  2. Getting products into the catalog
  3. Required fields for each product
  4. Product IDs must match the pixel
  5. Choose how to target
  6. Checklist
  7. Where AdPilot fits
  8. Sources

With Advantage+ catalog ads, you promote relevant items from an entire catalog, display ads for thousands of items to the right audience and automate the process (source). Meta’s documentation also refers to them by their older name, dynamic ads (source).

According to Meta, the solution has three parts (source):

  1. A feed from your catalog that delivers images, descriptions and prices into your ads.
  2. App Events or the Meta Pixel to measure actions (such as purchases) and build audiences.
  3. Ads built from your catalog that show relevant items to your audience.

1. What you need before creating a campaign

According to Meta, to create an Advantage+ catalog ads campaign you need (source):

  • A Facebook Page.
  • An ad account with registered payment information.
  • A catalog, such as a product catalog in your Meta Business Suite account.

You also need the Meta Pixel or App Events to measure actions such as purchases (source). In the Conversions API docs, server events are linked to a dataset ID and processed like events sent with the Meta Pixel (source). Setting it up and checking it: see Meta Pixel and Conversions API.

2. Getting products into the catalog

A catalog is an object (or container) of information about your products, and where you upload your inventory (source). According to Meta (source):

  • The most common approach is to list your products and attributes in a flat file (CSV, TSV, RSS XML, ATOM XML or Google Sheets) and upload it as a catalog feed.
  • Feeds can be uploaded manually or on a schedule: hourly, daily or weekly.
  • A Replace schedule refreshes the whole feed: items not in the feed file are deleted. An Update schedule changes selected items only.
  • A product (identified by its id field) can only be in one product feed at a time.
  • For near real-time updates to specific product fields, Meta offers the catalog Batch API.

3. Required fields for each product

If any of these fields are missing or formatted incorrectly, products may not upload to your catalog: id, title, description, availability, condition, price, link and image_link. You also need at least one of brand, gtin or mpn (Meta’s field table marks brand as required, so filling in brand is the safe choice), and one of google_product_category or fb_product_category (source). Rules worth knowing (source):

FieldRule
idA unique content ID for the item; use the SKU if possible. Each ID appears only once in the catalog.
titleUp to 200 characters; Meta recommends 65 at most to avoid truncation.
availabilityin stock or out of stock.
conditionnew, refurbished, used.
priceA number, a space, then the 3-letter ISO 4217 currency code, e.g. 9.99 USD.
linkStarts with http:// or https://, is valid and is hosted on your business’s website domain.
image_linkJPEG or PNG, at least 500 × 500 pixels, up to 8 MB.

4. Product IDs must match the pixel

For dynamic ads, an item’s id must exactly match the content ID for the same item in your Meta Pixel (source). So check that the two IDs match before you launch.

5. Choose how to target

Meta’s documentation describes three uses (source):

  • Retargeting: for example, people who viewed products in the last 3–5 days but didn’t buy.
  • Cross-sell or upsell to existing customers.
  • Broad audience: targeting by age, gender and other demographics, with relevant products from your catalog.

At ad set level, you specify a product set from your catalog to promote products from that set (source). In the Marketing API, the campaign objective for Advantage+ catalog ads can be PRODUCT_CATALOG_SALES, CONVERSIONS, LINK_CLICKS or APP_INSTALLS. When optimising for OFFSITE_CONVERSIONS, the default conversion event is PURCHASE (source).

Checklist

  • Facebook Page and an ad account with payment information
  • A catalog, connected to the ad account
  • The feed has the required fields; images ≥ 500 × 500, prices with a currency code
  • Replace or Update schedule chosen on purpose
  • Pixel running, and the product IDs it sends match the catalog id
  • Targeting chosen: retargeting, cross-sell or broad audience

Where AdPilot fits

For product catalogs, AdPilot for Meta Ads can propose creating, renaming and deleting catalogs; this needs the admin connection and goes through review (source). AdPilot deletes nothing without an approver’s agreement (source). Adding products and building the feed still happens on Meta’s side, as above.

💬 Need help? Join the ALFA Software support group on Telegram (ask in your own language) — or message our support bot privately about your account or invoices.

Checked against Meta’s documentation on 8 Nov 2026. Meta’s interface and documentation can change; where they differ from this article, follow Meta’s documentation.

Sources

  1. Meta for Developers — Advantage+ Catalog Ads: https://developers.facebook.com/docs/marketing-api/advantage-catalog-ads
  2. Meta for Developers — Get Started with Advantage+ Catalog Ads: https://developers.facebook.com/documentation/ads-commerce/marketing-api/advantage-catalog-ads/get-started
  3. Meta for Developers — Catalog: https://developers.facebook.com/docs/marketing-api/catalog
  4. Meta for Developers — Catalog overview: https://developers.facebook.com/docs/marketing-api/catalog/overview
  5. Meta for Developers — Catalog Fields: https://developers.facebook.com/documentation/ads-commerce/commerce-platform/catalog/fields
  6. Meta for Developers — Conversions API: https://developers.facebook.com/docs/marketing-api/conversions-api
  7. ALFA Software — AdPilot for Meta Ads: https://alfasoftwares.com/en/adpilot-meta