Catalog ads are like a bookshop owner who puts a different book on each customer's desk. The shelf (catalog) is one, but a visitor who browsed one section yesterday sees books from that section. The developer doc URLs still carry the name dynamic-ads.
It has three parts. First, a catalog feed that supplies images, descriptions and prices to the ads. Second, signals that measure actions such as purchases and build audiences, from app events or the Meta Pixel. Third, creating and delivering ads from the catalog. Signals are Search, ViewContent, AddToCart and Purchase events, each including a content_id. Unlike the Pixel, app events have no catalog ID field, so you must associate the catalog and app separately.
Supported campaign objectives are PRODUCT_CATALOG_SALES, CONVERSIONS, LINK_CLICKS and APP_INSTALLS. At the ad set level, promoted_object.product_set_id selects the set of products to promote; the conversion event defaults to PURCHASE and can be changed to something like ADD_TO_CART. A dynamic product audience is optional.
Weak signal events leave nothing to base the ad on. Check that catalog quality and the pixel's content_id values match first. Housing, employment, financial and political ads have their own special ad category limits.
When to use
Use it for large-catalog stores that want product-level personalization; matching signal events and catalog IDs come first.