Setting Up Meta Commerce: The Catalog, the Pixel and One Sale Counted Once

Today, we cover:

1. Checkout moved home. Meta's shops now send every purchase to your own website, which changes what your ads have to measure.
2. The catalog and the pixel. The product IDs in your events have to match the IDs in your catalog, and Commerce Manager shows whether they do.
3. Events Manager, browser and server. The pixel and the Conversions API report the same sale twice by design, and one shared ID makes Meta count it once.
4. California's SB 690. A new state law narrows one kind of lawsuit over tracking tags and leaves the rest standing.

The shop is now a window

Meta no longer completes sales inside Facebook or Instagram. Its help page on changes to Shops and checkout says purchases will always occur on the seller's website, where orders, payments, delivery and returns are now handled. Sprout Social dates the end of native checkout to September 2025. The shop in Commerce Manager still exists, but its job is display: a catalog of products, arranged into collections, that hands a shopper to a product page you host.

The change reaches into Ads Manager. The old "website and shop" conversion location is gone, and Meta tells advertisers to choose Website instead, leaving Shops switched on under personalised destinations so Meta can still send each person to whichever of the two is likelier to convert. The conversion events on offer stayed the same: view content, add to wishlist, add to cart, initiate checkout and purchase. Every one of them now happens on your site, which means Meta learns about them only if your site tells it.

The catalog and the pixel must use the same names

The catalog and the tracking are two halves of one system, and they meet at the product ID. Meta's developer guide to the pixel for Advantage+ catalog ads requires three events, ViewContent, AddToCart and Purchase, each carrying the IDs of the products involved, and those IDs must be the ones the catalog uses. If the catalog lists a shirt under one ID and the website reports it under another, Meta sees two unrelated things and cannot show the shopper the shirt they looked at.

Commerce Manager will tell you whether the halves agree. In the catalog's Events tab, Manage connections links a pixel to the catalog, and the same screen reports the catalog match rate, the share of product IDs in your events that match products in the catalog. The developer guide warns that the tab can take up to 24 hours to recognize newly tracked events, so an empty screen on the first afternoon is not yet a failure. A low rate after that points to the IDs, not to the tracking.

One sale, reported twice, counted once

Events Manager is where most setups go wrong, partly because Meta now asks for two feeds of the same data. The pixel reports what happens in the visitor's browser. The Conversions API reports the same actions from your server, out of reach of the browser's blockers. Meta recommends running both, and PPC Land's explainer on the pixel notes that Events Manager now groups the browser and server events for one property into a single dataset.

Running both means every purchase arrives twice. Meta's deduplication rules are exact: when a browser event and a server event share the same event name and the same event ID, and arrive within 48 hours of the first, Meta keeps one and discards the rest. Without that shared ID, Events Manager can report two sales where there was one, and the ads optimize toward a number that overstates the truth. The ID has to be created once and handed to both feeds, not invented separately by each.

The second grade Events Manager gives is how well each event can be tied to a real person. Meta calls it event match quality, and it depends on the customer details sent with the event. Meta ranks email and click ID as high priority; phone number, country and the business's own customer ID as medium; first name, city and ZIP code as low. An event can fire on time, every time, and still match poorly because it carries little to match on.

Some older steps no longer apply. Meta's page on Aggregated Event Measurement says advertisers no longer need to choose and rank eight conversion events per domain, that the Events Manager tab for doing so has been removed, and that domain verification is no longer required for event setup, though it may still be needed for other reasons. A guide that sends you looking for an event-ranking screen is describing a version of Events Manager that is gone.

Meta has also made the server half easier to start. According to PPC Land, a one-click, Meta-enabled Conversions API that mirrors pixel events from the server went live on April 27, 2026, and Meta began attaching product names and availability to pixel events automatically, with an opt-out in Events Manager. A mirror of the pixel can only contain what the pixel saw.

The law around the tag

California has changed the legal ground under these tags, though only in part. Governor Gavin Newsom signed SB 690 on Sept. 30, and Thompson Hine's summary explains that it ends private lawsuits under Section 638.51 of the California Invasion of Privacy Act, the pen-register provision that had become a common basis for suits over website tracking. Baker Donelson gives the effective date as Jan. 1, 2027.

The relief is narrow. Procopio notes that the attorney general can still enforce that section, and that claims under Section 631, the wiretapping provision, remain available against pixels and similar tools. Its advice to businesses is to keep an inventory of the tags on their sites, what each one sends and to whom, and whether the consent and disclosures behind them are adequate. That inventory is the same list a working Events Manager setup already requires.

Meta can only count what your site tells it, once, and by the right name.