When to run this checklist
Run it when a store first creates or connects a product catalog in Meta Commerce Manager, and before the first catalog ads campaign launches. Run it again after a replatform or a switch of data source, because the new source often changes product IDs, and a change of IDs breaks the match with every past pixel event. A catalog that was set up by an agency and is being moved to the business's own portfolio is a fresh setup for this purpose.
The person who manages the store's feed runs the catalog and ownership groups, the person who owns the Meta Pixel and Conversions APIServer-side event sharing with Meta. setup runs the events group, and the media buyer runs the product sets and ads groups. On a small team that may be one person; the order still matters, because product sets and ads cannot be checked until the events match.
Before you start
- Admin access to the business portfolio that will own the catalog, not a personal or agency portfolio.
- The data source: the feed file URL, the partner platform integration, or the pixel-based setup.
- The product ID scheme the site uses, and whether it differs for variants.
- Events Manager access for the pixel and the Conversions API, with a test route through view, add-to-basket and purchase.
- A margin and stock view of the catalogue, for building product sets.
- The ad account that will run catalog ads, and its existing audiences.
The checklist
The groups follow the chain: build the catalog, make the events match it, group the products, then check what the ads will show. Ownership comes last but is not optional, since a catalog nobody owns is the commonest reason a working setup stops working.
Catalog
Pixel and events
Product sets
Ads
Ownership
Where each check is explained
The widget keeps each line short enough to tick; the reasoning lives in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Catalog in the business's own portfolio | Catalog ads |
| Data source chosen | Catalog ads |
| Required fields and stable product IDs | Product feeds and Merchant Center |
| Feed schedule follows changes | Meta catalog products not showing |
| Pixel content IDs match the catalog | Setting up the Meta Pixel |
| Conversions API events deduplicated | Conversions API |
| Event match diagnostics checked | Meta catalog products not showing |
| Product sets by category, margin or stock | Catalog ads |
| Weak items kept out of prospecting | Shopping and catalogue ads for stores |
| Templates checked in every placement | Ad formats and placements |
| Recent purchasers excluded | Exclusions and audience overlap |
| Product pages agree with the ad | Product page optimisation |
| Catalog and feed owner | Marketing data operations and taxonomies |
| Access by role | Catalog ads |
If an item fails
The first catalog campaign waits. Catalog group failures are structural: a catalog created in an agency's or a person's portfolio can be lost when the relationship or the job ends, and product IDs that change with each feed export break every link between past events and products. Fix both before anything else, because fixing them later means rebuilding the catalog and losing its event history.
Events failures make catalog ads guess. If the content IDs in pixel events do not match the catalog IDs, the catalog's match diagnostics will show it, and RemarketingAdvertising to previous visitors or engagers. to product viewers will show the wrong products or fail to deliver. If the same events arrive through the pixel and the Conversions API without a shared event ID, purchases are counted twice and the campaign optimises toward inflated results; DeduplicationRemoving double counts when one conversion is reported by more than one source. is part of setup, not a refinement. Where the pixel and the feed use different ID schemes for variants, pick one and change the other, rather than trying to map between them.
Product set and ad failures are the media buyer's to fix. Prospecting sets full of out-of-stock or low-margin lines spend budget on products the business does not want to sell more of. Templates and overlays that look fine in the feed preview can cover the product or crop the price in Stories and Reels, so check each placement. If product pages disagree with the ad on price or stock, the fault is usually the feed schedule, which goes back to the catalog group.
A shoe retailer whose variants did not match
A footwear retailer called Corrowby connects its store platform's catalog integration and builds a retargeting campaign for people who viewed products in the last 14 days. The match diagnostics show that only about 40% of view events match a catalog item. The reason: the pixel sends the parent product ID, while the catalog lists each size as its own item with a variant ID. The developer changes the pixel to send the variant ID that the catalog uses, and the match rate rises above 90% within a few days. Before launch the media buyer also removes 70 sold-out lines from the prospecting set and excludes purchasers from the last 30 days from retargeting.
Common mistakes
- Building the catalog in the agency's portfolio. It works until the agency leaves, then access and history leave with it.
- IDs that change on every export. Each new feed looks like a new catalog to the events that came before.
- Parent IDs in the pixel, variant IDs in the feed. Products are viewed but never matched.
- Pixel and Conversions API without deduplication. Purchases double, and so does the reported return.
- One product set for everything. The ads spend most on whichever products are easiest to click, not most worth selling.
- Retargeting people who just bought. The same product follows a customer around after the order has shipped.
The catalog ads guide explains the format behind each group, and the checklists library holds the rest.
