Meta Ads Integration

Connecting a feed unlocks catalog-based ad formats that a single static ad cannot replicate at scale: dynamic ads that automatically show a shopper the exact products they viewed or added to cart, Advantage+ catalog campaigns that let Meta's delivery system pick the best-performing items from your whole inventory, and shoppable tags on Instagram and Facebook posts. Because every one of these formats reads live from the catalog, feed accuracy has a direct line to ad performance — a stale price or an out-of-stock item still marked "in stock" gets served to a shopper who then bounces, and repeated mismatches between your feed and your landing pages is a documented cause of items being flagged or disapproved in Commerce Manager.

Dynamic ads work by connecting two data sources: your product catalog (which supplies images, titles, prices, and stock status) and the Meta Pixel or Conversions API (which reports what a visitor did on your site — viewed a product, added it to cart, started checkout). The link between the two is the id field: Meta matches the content_id reported by the Pixel/CAPI event to the id of the corresponding item in your catalog. If these values don't match exactly, Meta cannot connect a shopper's on-site behavior back to a specific product, and dynamic retargeting for that item simply won't fire — which is why the id field should be a stable identifier (Meta recommends using your own SKU) that never changes between feed updates.

Commerce Manager accepts a product feed in CSV, TSV, RSS XML, ATOM XML, or a Google Sheets link; for programmatic updates, Meta also offers the Catalog Batch API and Direct Upload API. You can add a feed to Commerce Manager three ways: paste a feed URL for Meta to fetch on a schedule, upload a file manually from your computer, or link a Google Sheet that Meta re-fetches at scheduled times. CSV and XML feeds must be UTF-8 encoded, and all field names (plus certain supported values) must be in US English regardless of your store's market. If you use XML, it should follow the RSS 2.0 format with the Google product namespace declared as xmlns:g="http://base.google.com/ns/1.0", and special characters such as &, <, and > must be entity-encoded (&, <, >) since they aren't otherwise valid inside XML tag content.

The table below uses Meta's own catalog field names exactly as documented, so they map one-to-one onto the columns or XML tags Commerce Manager expects. For ecommerce items, at least one of brand, gtin, or mpn must be present in addition to the fields marked required below — Meta treats a missing product identifier as its own error class, separate from a missing required field.

1. Add your existing product source to Feedance — your current CSV, XML, Google Sheet, or platform export — as a data source.
2. Feedance maps your store's fields onto Meta's exact field names and formats: your price becomes price in the required "number + ISO 4217 code" format (e.g. 29.99 USD), your stock flag becomes the in stock/out of stock enum availability expects, and your category values get translated into the Google or Facebook product category taxonomy Meta requires for onsite checkout eligibility.
3. Feedance generates the feed in the format Commerce Manager needs — RSS 2.0 XML with the xmlns:g namespace and entity-encoded special characters, or CSV/TSV — so you don't have to hand-encode ampersands or manage the Google product namespace yourself.
4. Copy the generated feed URL into Commerce Manager under Catalog > Data Sources > Add > Data Feed, and set your scheduled fetch interval (hourly, daily, or weekly) so Meta keeps re-pulling the latest version automatically.

Commerce Manager lets you schedule a feed URL to be re-fetched hourly, daily, or weekly, and scheduled feeds cannot run more often than once per hour — for faster updates you need the Catalog Batch API or Direct Upload API instead of a scheduled URL fetch. How often you should actually update depends on how fast your inventory and pricing move: a daily fetch is usually enough for slow-moving catalogs, while stores with frequent price changes, flash sales, or fast-turning stock benefit from hourly updates so that price and availability shown in ads stay aligned with what's actually on the landing page — a persistent mismatch between feed data and the live page is a documented cause of items being flagged as showing incorrect or outdated information.

These are grounded directly in Meta's documented field behavior rather than general marketing advice:

1. Keep id stable and identical to the content_id your Meta Pixel or Conversions API sends — this is what lets dynamic retargeting connect a site visit to the right product.
2. Fill in google_product_category or fb_product_category as specifically as possible; a category is required for onsite checkout eligibility and helps Meta's delivery system match the item to the right audience.
3. Provide at least one of brand, gtin, or mpn for every item — this is a hard identifier requirement for ecommerce catalogs, not just a best practice.
4. Match your feed's price and availability to your live landing page on every update; Meta's crawler checks for this and stale data is a documented trigger for flagged items.
5. Use item_group_id to group size/color variants of the same product so Meta displays them as a single item with variant selection rather than as duplicate, competing listings.
6. Add extra angles via additional_image_link (up to 20 images) rather than relying on a single hero shot for image_link.

Does Meta Ads accept the same feed formats as Google Shopping?
Largely yes — Meta accepts CSV, TSV, RSS XML, and ATOM XML, the same broad format families most Google Merchant feeds use, plus a Google Sheets link option that Google does not offer.

What happens if my Pixel's content_id doesn't match my feed's id?
Dynamic ads and retargeting for that item will not work, because Meta links on-site behavior to catalog items strictly through matching content_id and id values.

Do I need both brand and GTIN?
No — Meta requires at least one of brand, gtin, or mpn per ecommerce item, not all three.

How fast can I update prices or stock?
Scheduled feed fetches can run as often as hourly (the fastest scheduled interval Commerce Manager supports); for near-real-time changes you'd need the Catalog Batch or Direct Upload API instead of a scheduled URL fetch.

Why is Meta showing an old price in my ad?
Meta's crawler periodically compares your feed data to your live landing page; if your feed hasn't been re-fetched since your price changed, the ad and Shop listing will keep showing the outdated value until the next fetch.

Can I use one feed for both Facebook and Instagram?
Yes — a single catalog and feed powers both Facebook and Instagram Shops, tags, and dynamic ads; there's no separate Instagram-specific feed format.

What image size does Meta require?
The image_link image must be JPEG or PNG, at least 500x500 pixels, and no larger than 8 MB.