Meta CAPI events missing — Purchase or AddToCart never shows in Events Manager.

Several products can look like “ads measurement is broken.” They do not share a settings panel. This page is only Meta Events Manager when Purchase or AddToCart from Shopify CAPI is missing (or arrives on only one of browser / server). Choosing whether to buy a pixel job or a 72-hour ops install is Meta pixel + CAPI vs ops install. Choosing GA4 / Shopify customer events versus that same install is GA4 Shopify vs ops install. Missing or double-firing across Klaviyo / Google / Meta at once is add-to-cart tracking. This page is only: Meta CAPI Purchase / AddToCart silence in Events Manager.

Six ordinary reasons those events never land usefully: wrong dataset or Meta channel disconnected, CAPI never enabled, Test Events never used so you are guessing, pixel and CAPI fire without matching event_id (dedupe fails), wrong event name or filters, or you tested a comparison / GA4 / multi-pixel page instead. Walk them in that order. You already pay for Shopify and Meta. You do not need another “pixel agency” to open Events Manager.

Open Shopify admin → Settings → Customer events / Facebook & Instagram (or the Meta / Facebook channel app you actually installed). Confirm the Pixel / dataset ID matches the one you open in Meta Events Manager — a leftover test pixel or an old ad account dataset looks identical to “Purchase missing.” If the channel shows disconnected, reconnect under a Business Manager user that still has access. Do not rebuild the whole ads stack first.

CAPI specifically: confirm Conversions API / server events are enabled for that dataset (Shopify’s Meta channel, a partner integration, or your own server). A browser pixel alone will not fill the server column. If CAPI was never turned on, enable it, save, and move to Test Events — that is the honest next proof, not a new app install.

Open Meta Events Manager → your dataset → Test Events. Paste the test code into Shopify’s Meta channel / pixel settings when the UI asks for it. From a phone or incognito session, add a product to cart and complete (or nearly complete) a test purchase. Watch which rows appear: browser only, server only, both, or nothing.

Browser-only with CAPI “on” usually means the server path is not connected or blocked. Server-only with a broken pixel means the theme / channel pixel is not loading on the storefront. Nothing at all means dataset mismatch or the event never fired. Screenshot the Test Events panel before anyone “fixes attribution” on a send that never left Shopify.

Meta expects the same event_name and a shared event_id on the browser pixel hit and the CAPI server hit so it can dedupe. If Shopify’s Meta channel sends CAPI without the matching browser event_id (or a custom snippet invents a second Purchase with a different id), Events Manager can look empty, sparse, or double-counted depending on the view. Prefer one owner: the official Meta / Facebook & Instagram channel on Shopify for both pixel and CAPI. Remove leftover theme snippets that fire a second Purchase or AddToCart.

Honest proof after a test checkout: both browser and server rows for Purchase (and AddToCart on the cart step) with the same event_id. If only one side has an id, fix the channel / snippet — do not add a third tracking app.

Standard Meta names matter: Purchase and AddToCart (not “Order completed,” not “ATC,” not a custom name your theme invented). If the store never reached thank you / order status, Purchase will not fire — that is expected silence, not a broken CAPI. If AddToCart is scoped only to a quick-add that your theme does not use, the event never leaves.

Also check Events Manager filters and date range: looking at yesterday while you tested today, or filtering to “browser only,” will look like missing CAPI. Clear filters. Widen the window. Then re-run one controlled test checkout.

Deciding whether Meta measurement and a 72-hour ops install are the same job is Meta pixel + CAPI vs ops install— not this page. GA4 / Shopify customer events versus that install is GA4 Shopify vs ops install. Missing or double-firing across Klaviyo, Google, and Meta at once is add-to-cart tracking. Those pages do not fix a disconnected Meta dataset or a missing event_id on CAPI.

The only honest test for this page: correct dataset, CAPI on, Test Events open, one AddToCart and one Purchase from a fresh session, browser + server rows with matching event_id in Events Manager. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: match the dataset, enable CAPI, run Test Events, align event_id dedupe, remove leftover snippets, confirm Purchase and AddToCart names. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: Meta pixel + CAPI vs ops install, GA4 Shopify vs ops install, add-to-cart tracking.

Pay for help when the work is not the Meta dataset toggle — it is connecting the stack you already have so lead capture is not dying in DMs, ops exceptions land in a channel you already check, and checkout-ready paths are one live workflow instead of a draft pixel plus a leftover snippet. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a Meta ads retainer, not a pixel agency rebuild, not a ROAS guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a Meta pixel / CAPI cleanup typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or ROAS claim.

What it does not buy: more orders, recovered revenue, better ROAS, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.