Facebook Custom Conversions let you define and optimize for a specific action that matters to your business, rather than relying only on Meta's standard events. They are genuinely useful, and they are still part of the setup in 2026. But the world around them has changed completely since most guides were written, and the honest truth is that even a perfectly configured Custom Conversion only ever measures what Meta itself can see. Here is how they work now, and where you still need to look beyond them.
A standard event is one of Meta's predefined actions, like Purchase or AddToCart. A Custom Conversion is one you define yourself, built from rules on your events and page URLs in Events Manager, so you can optimize toward a narrower or more specific action than the standard set covers. For example, you might create a Custom Conversion for purchases over a certain value, or for a thank-you page that only a particular product's buyers reach.
You build them in Events Manager by setting a rule, such as a URL containing a specific path, and naming the conversion. Meta then treats it as an optimization and reporting target you can select when you build campaigns.
If you set up Custom Conversions years ago, the surrounding machinery has changed enough that a refresher matters.
The Pixel is now a dataset. Your old Pixel ID is now your dataset ID, reflecting Meta folding browser and server events into one source.
The Conversions API is now standard. Browser-only pixel tracking lost reliability to iOS privacy changes, ad blockers, and short cookie lifetimes. In 2026 the standard setup is to run the Pixel and the Conversions API together and deduplicate them with a shared event ID, which recovers a meaningful share of otherwise-lost conversions and improves match quality. Your Custom Conversions should be firing through both.
Event limits and aggregation. Because of Apple's App Tracking Transparency, Meta measures iOS conversions through Aggregated Event Measurement, which reports in aggregate rather than at the user level and historically capped prioritized events per domain. Meta has automated much of this for web since 2025, but the takeaway stands, your conversion data from privacy-restricted users is aggregated and modeled, not precise.
Event Match Quality matters now. Meta scores how well it can match your events to users. Sending strong parameters through the Conversions API, like hashed email and phone, raises that score and improves both optimization and the accuracy of what Custom Conversions report.
Here is the honest part. You can configure Custom Conversions perfectly, run them through the Conversions API, and max out your Event Match Quality, and Meta will still only show you what Meta can see. That is the structural ceiling.
A Custom Conversion tells you Meta observed an action it believes one of its users took after seeing or clicking a Meta ad, within Meta's window, on Meta's increasingly aggregated and modeled terms. It cannot see the customer who first found you through Google weeks earlier, or the one who saw the Facebook ad but converted later through email on another device. Meta claims the conversions closest to itself and cannot account for the rest of the journey. Every platform grades its own homework, and a Custom Conversion is still Meta's homework.
So Custom Conversions are the right tool for one job, telling Meta's algorithm what to optimize toward so it delivers your ads to the right people. They are the wrong tool for deciding how to allocate budget across channels, because for that you need to compare Meta against everything else on neutral ground.
The complete approach is both halves. Configure your Custom Conversions and Conversions API well so Meta optimizes on the best signal you can give it. Then measure real performance with cross-channel multi-touch attribution that reconciles Meta against your actual sales and every other channel, so you can see which campaigns genuinely created customers rather than which ones Meta claimed.
That is what Wicked Reports adds on top of your Meta setup. It ties Meta ad clicks and the customers they produce back to real orders in your CRM, across devices and channels and across the full journey, so your budget decisions rest on reconciled revenue rather than Meta's self-reported view. Optimize inside Meta with Custom Conversions, then judge Meta from the outside with real attribution. See how it works in the platform overview, or book a demo to see it on your own data.
A Custom Conversion is an action you define yourself in Meta Events Manager, built from rules on your events and page URLs, so you can optimize toward a more specific action than Meta's standard events cover. An example is a Custom Conversion for purchases above a certain value or for a specific product's thank-you page. Meta then treats it as an optimization and reporting target in your campaigns.
Yes. In 2026 the standard setup runs the Meta Pixel and the Conversions API together, deduplicated with a shared event ID, and your Custom Conversions should fire through both. The Conversions API sends events server-side, which recovers conversions that browser-only tracking loses to iOS privacy limits and ad blockers, and improves the match quality Meta uses to optimize.
Because they only measure what Meta can see, on Meta's own aggregated and modeled terms. A Custom Conversion cannot account for the customer who first found you through another channel or who converted later on a different device, and Meta credits the conversions closest to itself. Judging cross-channel budget on Custom Conversions alone means trusting Meta's self-report. True ROI requires reconciling Meta against your real sales across every channel.
Use standard events for the common actions Meta's algorithm understands best, since they tend to optimize well, and use Custom Conversions when you need to optimize or report on a narrower action the standard events do not capture, such as a specific product or purchase value. Many advertisers use both. Whichever you use, send strong event parameters through the Conversions API to improve match quality.