When catalog performance moves, do not start by mechanically increasing budget. First verify that Meta receives consistent product and event data and that campaign structure reflects your economics.
Illustrative example: three different IDs
| Data | Illustrative value | Check |
|---|---|---|
| catalog id | SKU-BLUE-M | The ID of this exact catalog variant |
| content_ids | ["SKU-BLUE-M"] | The same item in an event using content_type=product |
| eventID / event_id | order-example-A | One shared ID for both copies of this purchase only |
These are synthetic technical values, not client data or ad results. For product_group, check item_group_id matching; do not swap variant and group IDs without checking the integration.
1. Product-data consistency
Titles, categories, prices, currency, availability, links, and identifiers should mean the same thing in the feed, on the site, and in events. Review errors and warnings in Commerce Manager and fix the root cause in the source system, not only in the exported file.
- Choose a variant and an item whose price changed.
- Save the source row, processed catalog item and URL.
- Check the last successful import and the next scheduled update: a manual catalog edit should not hide an incorrect export.
2. Eligibility and business rules
Ads may include products that are technically active but poor candidates for promotion: unavailable in the target region, incomplete, slow to ship, or unable to support the acquisition cost at their current margin.
- Open the product set actually used by the campaign, not just the whole catalog.
- Check delivery region, stock and excluded items.
- Record a reason and rule for an item that cannot be sold; do not delete the whole catalog to fix one card.
3. Pixel and Conversions API consistency
Browser signals can be incomplete, but server-side delivery is not a reason to duplicate events or bypass user consent. Compare event names, time, value, currency, and item IDs. For events sent through both channels, configure deduplication with a consistent event ID.
- For one test purchase, compare both copies of Purchase.
- The browser eventID and server event_id must identify the same event; the name must match too.
- A new order needs a new event ID.
- Check repeated submissions from a single channel separately.
4. Audiences as suggestions, not prerequisites
In Meta Advantage+, audience inputs can act as suggestions before the system searches more broadly. A lookalike or customer list may be a useful signal when the data is sufficient and lawfully collected, but it is not a mandatory launch condition.
- Check which fields your interface labels Audience controls and which are suggestions.
- Do not automatically treat an entire age range or customer list as a hard constraint.
- Record actual delivery and permitted-audience restrictions and check the effective expansion.
Meta: Audience controls / suggestions ↗
5. Creative and delivery context
Catalog format does not remove the need to explain why someone should buy from you. Review images, titles, price, offer, and landing page. Separate acquisition and re-engagement messages only when those segments can be measured reliably.
- Preview the ad with several catalog items, not just its first card.
- Titles should distinguish variants, images should show the product, and links should open the same offer.
- Check automatic creative enhancements if enabled.
6. Diagnostics in Commerce Manager
Use Commerce Manager—not Google Merchant Center—to diagnose a Meta catalog. Review rejected items, data-source issues, event-to-item matching, and product availability in the markets you target.
- Catalog match rate concerns matching events to catalog items, not matching a person.
- Meta describes a 28-day window with up to 48 hours of reporting delay.
- A specific catalog and all connected catalogs can show different rates.
- Download issue examples and recheck after processing.
7. Campaign structure based on economics
One campaign may be appropriate when products have similar economics and enough data for optimization. Separation can make sense when budgets, countries, goals, margins, promotions, or availability rules genuinely differ.
- Separate Meta conversion value, paid orders and profit.
- Reconcile returns, margin, conversion lag and attribution window.
- A structure change should serve a specific budget or assortment decision, not an arbitrary SKU count.
What to do after the checks
This checklist is not a forecast. It helps separate data, setup, and business-logic issues from normal auction variability. Record the baseline, change one material element at a time, and assess results within an agreed attribution window.
Catalog advertising questions
Are Meta Catalog Sales, DPA and Advantage+ catalog ads different?
DPA and Catalog Sales appear in older guides. The current format name is Advantage+ catalog ads. Do not confuse the catalog format with Advantage+ audience or whole-campaign automation; check the settings available in your account.
Do I need both content_ids and contents?
The official instructions allow content_ids or contents. Send the corresponding item or group IDs and check the content type. contents also includes quantity. One plugin’s field or format is not a substitute for inspecting the actual event.
Should event_id equal the product ID?
No. The product ID connects an event with the catalog. event_id identifies a particular action for Pixel/CAPI deduplication. Both copies of one Purchase share an event ID and name; different purchases must not share one constant event ID.
Does high Event Match Quality guarantee ads for the right products?
No. EMQ concerns matching an event to a person; catalog match rate concerns matching it to an item. Check both diagnostics, product availability and actual sales separately. Neither score guarantees ROAS.
Does CAPI replace consent or advertising checks?
No. Server-side transmission is not a way around consent, Meta rules or data requirements. It does not fix wrong product IDs or an unavailable checkout. Check lawful data transmission and integration behavior.
Sources and limits
Checked October 11, 2026. This is UPLIFY’s diagnostic method, not a sales guarantee or an explanation of every Meta decision. Setting labels and availability may vary by account.
- Meta: Advantage+ catalog ads ↗
- Meta: Catalog events and parameters ↗
- Meta: Catalog match rate ↗
- Meta: Pixel/CAPI deduplication ↗
- Meta: Pixel parameter reference ↗
- Meta: Audience controls / suggestions ↗
Related services and tools
Investigate your store’s catalog
Send the store URL and describe the catalog issue, without passwords or customer personal data. We will agree checks of the feed, events and ads.
