The Pixel/CAPI combo is the standard conversion-tracking architecture for any business running paid ads on Meta in 2026.
Meta Pixel
JavaScript code installed on a website that fires events to Meta when users take specific actions: page view, lead form submit, button click, purchase. The Pixel was the foundation of Meta’s ad targeting for years, but its accuracy degraded after Apple’s iOS 14.5+ App Tracking Transparency changes that limited what the Pixel could see for iOS users.
Conversions API (CAPI)
Server-side conversion tracking that sends events directly from your backend (CRM, web server) to Meta’s servers. CAPI bypasses browser-level privacy restrictions and provides more reliable conversion data than the Pixel alone. Critical for B2B operations where 30-50% of leads come from iOS Safari users whose Pixel data is fragmented.
Pixel + CAPI deduplication
When both Pixel and CAPI fire for the same event, Meta needs to know it’s one conversion, not two. The deduplication mechanism uses an event_id parameter shared between client-side Pixel call and server-side CAPI call. Same event_id = same event = counted once.
Mortgage CRM and CAPI
BNTouch’s CAPI architecture (developed with Yuri’s team) supports two-event funnels: a Lead event fires immediately on form submission, a QualifiedLead event fires when sales moves the lead to validated status. Meta optimizes campaigns toward QualifiedLead while still receiving Lead events for attribution. Each tenant configures their own Meta Pixel ID and CAPI Access Token in BNTouch settings.