The Meta Pixel tracks website actions from Facebook and Instagram ad clicks. The Conversions API (CAPI) sends conversion data directly from your server — capturing events the Pixel misses due to ad blockers, iOS privacy changes, and browser restrictions. Together they give Meta's algorithm the accurate signal it needs to optimise toward real business outcomes.
The Meta Pixel is a snippet of JavaScript code installed on your website that fires events when users take actions — page views, contact form submissions, purchases, add-to-carts. This data is sent to Meta and used for three purposes: conversion tracking (measuring what your ads are generating), retargeting audience building (creating custom audiences from website visitors), and campaign optimisation (telling Meta's algorithm what to optimise toward). The Conversions API (CAPI) is a server-side complement to the Pixel. It sends conversion events directly from your web server to Meta's servers — bypassing browser-based restrictions from iOS 14+ privacy changes, Safari ITP, and ad blockers that prevent the Pixel from firing. Together, Pixel plus CAPI provides the most complete picture of conversion activity and gives Meta's algorithm the accurate signal needed for effective Smart Bidding. At Scalepoint, both are installed and verified before any Meta campaign goes live.
Apple's iOS 14 App Tracking Transparency update (2021) and subsequent Safari Intelligent Tracking Prevention changes significantly reduced the accuracy of browser-based pixel tracking. Studies across the industry found that Meta Pixel alone now misses 15–40% of conversion events on iOS devices — meaning Meta's algorithm is being optimised on incomplete data. For Australian businesses where a significant portion of their audience uses iPhones (approximately 55% of Australian smartphone users are on iOS), this is a material accuracy problem. The Conversions API solves this by sending conversion data server-side — not through the browser — where iOS privacy restrictions cannot intercept it. Meta's own data shows that CAPI implementation improves reported conversions by 15–30% on average by recovering events that browser-based tracking was missing (Meta, 2025).
of Australian smartphone users are on iOS — making iOS tracking loss a material issue for all Meta advertisers in Australia
improvement in reported conversion accuracy after CAPI implementation — recovering events browser tracking was missing (Meta, 2025)
decrease in cost per acquisition after fixing conversion tracking and enabling accurate Smart Bidding signals (Scalepoint client, FY25)
Pixel plus CAPI implementation, event verification, and ongoing monitoring — the complete tracking foundation.
Meta Pixel installed via Google Tag Manager with base code on every page and standard event tracking on contact forms (Lead), purchases (Purchase), and quote requests (CompleteRegistration). We verify every event fires correctly in Meta's Events Manager before any campaigns go live.
CAPI implementation sending key conversion events (leads, purchases) directly from your server to Meta — capturing what the browser Pixel misses. Deduplication configured to prevent double-counting events that both Pixel and CAPI capture. We implement via direct API integration or Meta's partner integrations (Shopify, WooCommerce, and major platforms have native CAPI support).
Event Match Quality (EMQ) score determines how accurately Meta can match conversion events back to the Facebook user who converted. We implement customer information parameters (hashed email, phone, name where available) to improve EMQ — higher EMQ means better attribution, better lookalike audiences, and more effective Smart Bidding.
Beyond standard events, we set up custom conversions for actions unique to your business — specific form submissions, page visits that indicate high intent, video completions, or scroll depth thresholds. Custom conversions allow campaign optimisation toward the specific actions that map to your business outcomes.
The Pixel powers all website-based retargeting audiences — visitors to specific pages, time-based segments (visited in last 7/14/30 days), and action-based segments (visited pricing page, started but did not complete a form). These audiences are built from the moment the Pixel is installed — the sooner it goes live, the sooner retargeting can begin.
Meta's Events Manager is reviewed every week as part of campaign management — checking event volume trends, EMQ scores, and error alerts. Tracking drift (events stopping firing, deduplication breaking) can go unnoticed for weeks in unmonitored accounts, causing Smart Bidding to optimise on degraded data.
Before any Meta campaign goes live, the Pixel and CAPI need to be installed and verified. We treat this as a prerequisite — not an optional add-on. Running Meta Ads without accurate conversion tracking is spending budget without the ability to optimise or measure.
Many businesses running Meta Ads since before 2021 have Pixel-only setups that have never been updated for iOS 14 changes. If your Meta reporting shows declining conversion volume that does not match your actual business results, tracking degradation is likely the cause. A CAPI implementation audit and upgrade typically recovers 15–30% of reported conversions.
For ecommerce, CAPI integration with Shopify, WooCommerce, or BigCommerce recovers purchase events lost to iOS privacy — critical for Target ROAS bidding, which depends on accurate purchase data. Most major ecommerce platforms now have native CAPI support that we configure as part of setup.
Account migrations frequently break tracking — pixels transferred incorrectly, CAPI connections dropped, event deduplication broken. A full tracking audit and rebuild is part of every new Meta account onboarding at Scalepoint.
No call required. Tell us your business and goals — we send back a written audit within 3 business days.