A catalog with a performance signal on every product
Meta reads your products from the feed. Feedance sends a complete, valid feed plus the signals Meta does not have on its own.
Facebook Dynamic ADSChannel · Ad platformsFeedance builds your Facebook Dynamic ADS feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.
Meta reads your products from the feed. Feedance sends a complete, valid feed plus the signals Meta does not have on its own.
Facebook Dynamic Ads (now largely rebranded by Meta as Advantage+ catalog ads) are an ad format that assembles individual product ads automatically from a Commerce Manager product catalog, instead of an advertiser building one ad per SKU. Rather than a single static creative, Meta's ad engine pulls the title, image, price, and availability for a specific id in your feed and renders it into an ad template at serve time.
This page is not a repeat of the general Meta Ads / Commerce Manager catalog setup already covered on our Meta Ads integration page. It focuses specifically on what makes Dynamic Ads a distinct format: the retargeting mechanic that reconnects a shopper with the exact product they viewed or added to cart, the Pixel/Conversions API content_id matching that makes that reconnection possible, and the dynamic creative (price overlays, sale badges, frames) that gets stamped onto catalog images per product.
Dynamic Ads only work as well as the catalog behind them. Because the ad creative, price, and availability shown to a shopper are pulled live from your feed's fields, a feed that is stale, incomplete, or inconsistently formatted directly degrades ad relevance and can cause products to be rejected from the catalog entirely.
A feed management layer matters more for Dynamic Ads than for most other channels because the format is built around scale (advertisers routinely run catalogs of thousands of SKUs that could never be turned into individual ads by hand) and around freshness (a sold-out or repriced product still being shown to a retargeted shopper is a direct trust and ROAS problem, not just a minor inconsistency).
This is the mechanic that differentiates Dynamic Ads from a standard Meta catalog listing. Dynamic Ads run on three product events fired by the Meta Pixel and/or Conversions API (CAPI): ViewContent, AddToCart, and Purchase. Each event carries a content_ids parameter (an array of one or more IDs) and a content_type value of product or product_group.
Meta matches those content_ids against the id (or, for variant-level matching, the item_group_id) values in your product catalog feed. The match is an exact, case-sensitive string comparison — if your website's Pixel fires SKU-001 and your feed lists the same product as sku-001, Meta treats them as two different products and the retargeting link breaks silently for that item.
You can monitor how well this is working in Events Manager under Diagnostics → Pixel → Catalog Match Rate, which reports the percentage of product events that were successfully matched to a catalog item. A low match rate means Meta cannot reliably tie a shopper's on-site behavior back to a specific product, which quietly shrinks your retargeting audience and creative pool even if the catalog itself looks healthy in Commerce Manager.
A common real-world cause of match-rate drops is a parent-vs-variant ID mismatch: some storefronts (Shopify is a frequently cited example) fire the specific variant ID in content_ids while the feed lists only the parent product ID, or vice versa. Keeping your feed's id/item_group_id values aligned with whatever ID your Pixel and CAPI implementation actually sends is the single highest-leverage fix for Dynamic Ads performance.
Dynamic Ads pull from the same Commerce Manager catalog infrastructure as other Meta catalog-based formats. Meta accepts catalog feeds in CSV, TSV, XML (RSS/ATOM-style), XLSX, or Google Sheets, submitted either as a one-time file upload or as a scheduled feed that Meta fetches automatically from a hosted URL (the URL must begin with http, https, ftp, or sftp and must point directly to the feed file, not to a storefront or Page).
For catalogs that change price or stock levels frequently, the Catalog Batch API offers a programmatic alternative that pushes updates directly rather than waiting on the next scheduled fetch. Compressed feeds (ZIP or GZIP) are also supported, provided the uncompressed file is CSV, TSV, or XML.
The core catalog fields below are required (or effectively required) for a product to be eligible to serve in a Dynamic Ad. Because Dynamic Ads depend on the id field for Pixel/CAPI matching, keeping it stable across every feed update is more critical here than for other catalog uses.
| Attribute | Required | Format / Notes |
|---|---|---|
id | Yes | Unique per product, max 100 characters; must exactly match the content_id your Pixel/CAPI events send for that product |
title | Yes | Max 200 characters (roughly 65 recommended for visibility in ad placements) |
description | Yes | Plain text, max 9,999 characters; should differ from the title |
availability | Yes | in stock or out of stock; stale values cause sellable products to be hidden or sold-out products to keep serving |
condition | Yes | new, refurbished, or used |
price | Yes | A number followed by an ISO 4217 currency code, e.g. 19.99 USD; a missing currency code invalidates the item |
link | Yes | Valid URL to the product's page on your own domain |
image_link | Yes | JPEG or PNG, minimum 500x500px (1024x1024px recommended) |
brand | Recommended | Max 100 characters; used for retargeting and filtering by product set |
item_group_id | Conditional | Required to group size/color variants under one parent so Dynamic Ads can match and display the correct variant |
Feedance builds and maintains the Meta-compliant catalog feed that sits behind your Dynamic Ads setup, so the mapping and matching work described above doesn't have to be done by hand in a spreadsheet.
id, title, price, availability, condition, image_link, link, brand, item_group_id), normalizing formats such as the price-plus-currency-code requirement and the exact in stock/out of stock availability strings.id value for each product stable across every export, which is the field your Pixel/CAPI content_id events must match — the single most common point of failure in Dynamic Ads setups.Meta supports scheduled feed fetches on an hourly, daily, or weekly cadence, plus the option of direct, event-driven updates through the Catalog Batch API for advertisers who need near-real-time changes.
Because Dynamic Ads are retargeting-driven, feed lag has an outsized effect: a shopper who added an item to cart yesterday and is retargeted today should not see a price that changed overnight or a product that has since sold out. Catalogs with volatile pricing, flash sales, or fast-moving inventory should run on the more frequent end of Meta's scheduled options (hourly) or move to the Batch API; slower-moving catalogs can generally run on a daily schedule without hurting match quality.
content_ids sent by the Pixel or CAPI don't match any id in the catalog, so Meta can't link the browsing event to a product. Checked in Events Manager → Diagnostics → Pixel → Catalog Match Rate.item_group_id structure.SKU-001 in the feed versus sku-001 in the Pixel event are treated as two different products, silently breaking retargeting for that item.price value without an ISO 4217 currency code invalidates the entire product row.availability value that lags real stock either hides sellable inventory from ads or keeps advertising products that are already sold out.event_id from both the browser Pixel and server-side CAPI lets Meta deduplicate the two signals into one event, which recovers otherwise-lost match data without inflating counts.How is this different from the Meta Ads / Commerce Manager catalog I already have set up? The catalog itself is the same underlying object; Dynamic Ads is the retargeting-focused ad format built on top of it, driven by matching Pixel/CAPI content_id events back to catalog products. Standard catalog listings (like Shops) don't depend on that event-matching layer the way Dynamic Ads do.
Do I need the Meta Pixel, or is CAPI enough? Dynamic Ads can run on Pixel alone, CAPI alone, or both together; running both with a shared event_id for deduplication is Meta's recommended setup for the most complete match data.
What happens if a product's content_id doesn't match my catalog? That product's on-site view/cart/purchase activity can't be linked to a catalog item, so it's excluded from retargeting audiences and dynamic creative for that item, which shows up as a drop in Catalog Match Rate.
Can Dynamic Ads show a specific size or color a shopper viewed? Yes, provided the catalog uses item_group_id to group variants under a shared parent and the Pixel/CAPI events send the matching variant-level ID.
How fast do feed changes show up in live Dynamic Ads? As fast as your feed update method: within the hour on an hourly scheduled fetch, or near-instantly when pushed through the Catalog Batch API; a daily or weekly schedule will lag price and stock changes accordingly.
Facebook Dynamic Ads is an advertising platform offered by Facebook that allows businesses to promote their products or services to a targeted audience. It was launched in the year 2015.
The country of origin of Facebook is the United States, as it was founded by Mark Zuckerberg and his college roommates in Harvard University in 2004. However, the Dynamic Ads platform is available worldwide and can be accessed and utilized by businesses from various countries.
Facebook Dynamic Ads provide businesses with a powerful tool to create personalized and highly relevant ads. The platform uses a combination of user data, such as browsing behavior, interests, and demographics, to dynamically deliver ads to users who have shown interest in similar products or services.
With Dynamic Ads, businesses can create a catalog of their products or services and set up automated rules to showcase the most relevant items to their target audience. These ads can be displayed on various placements across Facebook, including the news feed, sidebar, and Instagram.
The platform also allows businesses to retarget their website visitors or app users, showing them ads featuring the exact products or services they have previously viewed. This personalized approach helps increase conversion rates and drive sales.
One of the key features of Facebook Dynamic Ads is the ability to customize the ad content dynamically. This means that the platform automatically pulls in relevant product details, such as images, titles, descriptions, and prices, from the catalog to create the ad. By leveraging this feature, businesses can save time and resources on manual ad creation while delivering highly personalized and visually appealing ads.
Furthermore, Facebook Dynamic Ads also provides businesses with detailed performance insights, allowing them to measure the success of their campaigns with metrics such as impressions, clicks, and conversions. These analytics enable businesses to optimize their campaigns and improve their return on investment.
In summary, Facebook Dynamic Ads is a powerful advertising platform that was launched in 2015, originating from the United States. It provides businesses worldwide with the ability to create personalized and highly relevant ads by leveraging user data and automation.
Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.