Meta Pixel Conversions API is the setup every South African Meta advertiser should have had since 2022, and most still do not. Running the Pixel on its own has been an obsolete configuration since iOS 14 broke browser tracking. Meta reports the conversions its algorithm can measure, and modelled data fills the rest with educated guesses. On most SA accounts we audit, the Pixel is under-reporting conversions by 20% to 60%, and the ad delivery is suffering because the algorithm has less real data to learn from.
This is the practical 2026 version: what the Meta Pixel Conversions API actually does, how to install it on a South African site, and the eight events every account should send to give Meta enough data to run properly.
What the Meta Pixel Conversions API does
The Pixel is a piece of JavaScript that runs in the visitor’s browser and reports events (page views, add-to-cart, purchase) back to Meta. iOS 14, cookie restrictions, ad blockers, and privacy settings each blocked a slice of that data. On a typical SA store in 2026, 25% to 50% of real conversions never reach the Pixel.
The Conversions API is a server-to-server integration. Your server sends the same events directly to Meta, with more identifying information (hashed email, phone, IP, user agent). Meta then deduplicates against Pixel events, so no double-counting, but it recovers the events the Pixel missed. Together, Pixel + CAPI gives Meta a near-complete view of what happened, and the algorithm rewards the account by running better.
The 8 events every SA account should send
- PageView: every page load. Baseline.
- ViewContent: product or key content page view. Fires on product pages, service pages, and blog posts you care about.
- AddToCart: WooCommerce, Shopify, or custom cart event. Critical for retargeting.
- InitiateCheckout: the customer starts the checkout flow. Second-strongest predictor of purchase after AddToCart.
- Purchase: completed sale with real ZAR value and currency. Without the value, the algorithm cannot bid on ROAS.
- Lead: form submission, contact enquiry, or booking. Value is optional but helpful.
- CompleteRegistration: account creation, newsletter signup, whitepaper download.
- Contact: phone call click, WhatsApp click, email click. Meta counts each as a soft conversion.
Every event should include the customer’s hashed email and phone number where available, plus the event ID for deduplication with the Pixel. Missing customer data drops your Event Match Quality; missing event ID causes double-counting.
How to install Meta Pixel Conversions API on an SA site
The path depends on your platform:
- WooCommerce: the official Facebook for WooCommerce plugin handles Pixel + CAPI in one install. It captures Purchase, AddToCart and InitiateCheckout with correct values automatically. Configure it, test with the Meta Test Events tool, done.
- Shopify: Shopify’s built-in Facebook & Instagram sales channel handles CAPI automatically. Older stores may still be on the legacy pixel; migrate.
- WordPress with a form plugin (Fluent Forms, WPForms, Gravity): use PixelYourSite Pro or a similar plugin that supports server-side events for Lead and Contact. Free plugins often stop at browser-side only.
- Custom or headless sites: a developer needs to POST events to the Meta Graph API from the server that handles the conversion (order confirmation, checkout webhook, form submit handler). Include event ID for dedup.
- Any platform via the Conversions API Gateway: a free Meta-provided proxy you host on your own subdomain that sends events server-side without deep developer work. Best for lean SA teams.
Testing that it actually works
- Open Meta Events Manager and go to Test Events for your pixel. Enter your site URL, load the site, and trigger a conversion. Both the Pixel and CAPI events should appear, and Meta should show them as a matched pair (one event, sent both ways).
- Check Event Match Quality per event under Diagnostics. Anything below 6 needs more customer data added to the CAPI payload; anything above 8 is healthy.
- Wait 48 hours and check the Aggregated Event Measurement configuration. Meta ranks your top 8 events; if your most important event (usually Purchase or Lead) is not in the top 4, other events are cannibalising the slot.
- After 14 days, compare CAPI + Pixel conversion count against your CRM or Shopify admin. Total should be within 10% to 15% of your real number.
The common Meta Pixel Conversions API mistakes on SA accounts
- CAPI installed without event IDs, so every conversion is double-counted. Reporting looks great; ad delivery gets confused.
- Purchase event without a value or currency. Currency defaults to USD in some setups, which breaks ROAS bidding for ZAR accounts.
- Multiple pixels installed via different plugins (Facebook for WooCommerce + PixelYourSite + a hardcoded pixel). Deduplication breaks; conversion counts inflate.
- CAPI running but no customer data attached (no email, no phone). Event Match Quality stays at 4-5 and the algorithm cannot use the events effectively.
- Test Events verified once, then never checked again. Setup drifts as plugins update.
What good Meta tracking looks like for an SA business
Pixel + CAPI installed, sending the 8 events above with real values and customer data. Event Match Quality of 8+ on Purchase and Lead. Reported conversions in Meta within 10-15% of your real conversion count from CRM or store admin. Modelled conversions under 20% of total. When those conditions hold, the algorithm has enough data to optimise properly, and Advantage+ and retargeting campaigns start earning what they should.
For the wider Meta view including Advantage+ Shopping, budget levels and campaign structure, see Meta Advantage+ Shopping in South Africa and how Meta ads work for SA businesses. This tracking setup is the foundation those campaigns run on; without it, everything else is guesswork.
