Foreground CAPI Health Check is now live on WordPress.org
A free 12-check audit for any WordPress site's Meta Pixel and Conversions API setup. No signup, no email capture, no phone-home.
Foreground CAPI Health Check is now live on WordPress.org. A free 12-check audit for any WordPress site's Meta Pixel and Conversions API setup. No signup. No email capture. No phone-home.
The problem we kept seeing
Most WordPress sites running Meta Ads are losing around 30 percent of their attribution to broken Pixel and Conversions API tracking. The browser Pixel alone stops reporting events for a meaningful share of visitors after iOS 17 and iOS 18 changed how Apple devices handle tracking. Server-side CAPI is the documented fix, but most implementations we have audited are partial, and the gap is invisible from inside Meta Events Manager.
The typical market response to this gap is an agency quote between $1,500 and $5,000, often with no clear diagnosis of what is actually broken. Marketing managers either pay the quote without understanding what they are paying for, or do nothing and accept the attribution loss as the cost of running Meta Ads in 2026.
We built Foreground CAPI Health Check because there was no audit-first option.
What the plugin does
Foreground CAPI Health Check is a free WordPress plugin available on the official WordPress.org plugin directory. It runs a 12-check audit against the 2026 Meta tracking stack on any WordPress site, scores the result 0 to 100, and explains each failure in plain English with difficulty-rated DIY fix steps.
The 12 checks fall into five categories:
Foundation (4 checks): Pixel installed and parseable, domain verification, events firing, HTTPS enforced.
Match Quality (3 checks): Advanced Matching, fbclid first-party capture, external\_id in Advanced Matching.
Reliability (2 checks): CAPI deduplication via eventID, server-side CAPI plugin presence.
Compliance (2 checks): Consent Mode v2, Apple Privacy Manifest readiness.
Optional (1 check): Google Tag Manager container.
The plugin makes a single HTTP request to the site's own front page and parses the rendered HTML. No data leaves the site. No signup, no email capture, no third-party calls. The audit runs only when a WordPress administrator clicks the Run audit button inside Tools, Meta CAPI Health.
Why iOS broke Meta tracking
Three Apple privacy mechanisms compound to reduce browser Pixel reliability.
App Tracking Transparency (iOS 14.5, April 2021). The prompt that asks users whether an app may track them across other companies' apps and websites. The majority of Apple users opt out. The browser Pixel can no longer rely on Apple device identifiers for matching, and event data quality degrades accordingly.
Link Tracking Protection (iOS 17, September 2023). This strips known tracking parameters, including the fbclid that Meta uses for click attribution, from URLs in Mail, Messages, and Safari Private Browsing. A click from a Meta ad that lands on a WordPress site via Mail will not carry the fbclid that Meta needs to attribute the conversion. The browser Pixel sees the visit but cannot connect it to the ad.
iOS 18 (September 2024). Expanded both mechanisms. Hide My Email is more widely adopted, which obscures email-based Advanced Matching. Private Browsing applies more aggressive parameter stripping. The same patterns now apply to a larger share of traffic.
The cumulative effect is that browser-side tracking alone misses a meaningful share of conversions on any site that takes traffic from iPhone users, which is most sites.
Why Conversions API is the answer, and why most installs are still broken
Server-side Conversions API sends event data from the WordPress server directly to Meta, alongside hashed customer information and an explicit eventID for deduplication against the browser Pixel. When implemented cleanly, it recovers most of the iOS attribution gap. When implemented partially, which is the more common state, it produces a worse outcome than running with Pixel alone, because Meta now sees the same conversion twice and learns from corrupted signal instead of degraded signal.
The five failure modes that surface most often inside the diagnostic:
CAPI installed but no eventID dedup, so Meta double-counts events. fbclid not captured server-side, so server events lack click attribution. Advanced Matching parameters not hashed correctly, so match quality stays low. Server events missing required fields (event\_source\_url, action\_source). Apple Privacy Manifest not declared, which trips warnings inside iOS 17.4 and higher.
These map to checks 4, 5, 6, 8, 9, and 11 inside the Foreground CAPI Health Check report. They are precisely the failures an agency invoice for "CAPI implementation" should have prevented. Often did not.
How to use it
Install Foreground CAPI Health Check from the WordPress.org plugin directory, activate it, and click Run audit on this site under Tools, Meta CAPI Health. The audit completes in under a minute.
If the score is 85 or above, the stack is solid and no further work is needed. The plugin will tell you so directly.
If the score is below 85, the dashboard expands each failure with two columns: what the failure means, and how to fix it. The easy fixes (Advanced Matching, HTTPS, domain verification) can be done in under an hour inside Meta Business Manager and the WordPress admin. The hard fixes (server-side CAPI endpoint, eventID deduplication, fbclid first-party capture) typically require PHP development.
Each re-run is recorded. The score history panel shows progress as fixes land. The 20 most recent runs are kept for visual trend tracking.
When to hire someone
If the plugin reports a score below 85 and PHP development is not in scope, Foreground offers a flat $497 Pixel Fix delivered in 4 business days. The engagement is scoped from the plugin's audit output rather than a discovery call, and the price is meaningfully below typical agency quotes for the same work.
The reason for releasing the plugin is to make sure anyone who pays for the Pixel Fix actually needs it. The audit-first model means we do not sell remediation to sites that do not have a remediation problem.
Install
Foreground CAPI Health Check is available now at wordpress.org/plugins/foreground-capi-health/. The plugin works with any WordPress site running version 6.0 or higher and PHP 7.4 or higher. It coexists cleanly with PixelYourSite, Meta for WordPress, CAPI Suite, GTM for WordPress, Cookiebot, CookieYes, Complianz, and other common tracking and consent stacks.
Written by Foreground Digital. Start a project →