Khmer Lugod

Foreground Digital

The browser Meta Pixel is broken for ~30% of your visitors after iOS 17 and iOS 18 changed how Apple devices handle tracking. Most marketing managers running WordPress have no easy way to tell if their Pixel + CAPI setup actually works.
This plugin runs a 12-check audit against your site’s front page and gives you a score from 0 to 100, plus plain-English explanations of what each failure means and how to fix it.
Free forever. No signup, no upsell harassment, no phone-home. Every audit runs locally on your server.
Need it fixed for you? If your score is below 85 and you’d rather not learn server-side CAPI from scratch, we offer a flat-fee Pixel Fix service: $497, delivered in 4 business days. One link to that service appears inside the plugin admin only when your score is below 85. The audit works completely whether or not you use the paid option.
What it checks
<ul>
<li>Meta Pixel installed and parseable</li>
<li>Domain verification (iOS 14+ critical)</li>
<li>Pixel events firing (PageView, Purchase, Lead, etc.)</li>
<li>Advanced Matching (the single biggest EMQ lever)</li>
<li>CAPI deduplication via eventID</li>
<li>Consent Mode v2 / cookie banner presence</li>
<li>Google Tag Manager container</li>
<li>fbclid first-party capture (iOS 17 / iOS 18 Link Tracking Protection)</li>
<li>external_id in Advanced Matching (iOS 18 Hide My Email answer)</li>
<li>Server-side CAPI plugin presence</li>
<li>Apple Privacy Manifest readiness (if you link to an iOS app)</li>
<li>HTTPS enforced</li>
</ul>
What it does NOT do
<ul>
<li>No phone-home. Every audit runs on your server against your URL. Nothing is sent to Foreground.</li>
<li>No email capture. No signup wall.</li>
<li>No subscription, no paid tier, no upsell harassment.</li>
<li>No automatic re-runs or cron jobs.</li>
</ul>
Made by Foreground Digital
Foreground is a Dubai-based digital agency. We build Meta Ads campaigns and the server-side infrastructure that catches them — Pixel + CAPI, CRM integrations, WordPress + headless. Founded 2024.
<h3>External services</h3>
This plugin makes ONE outbound HTTP request, and it goes only to your own WordPress site. No data is ever sent to Foreground, Meta, or any other third party.
1. Your own site’s home URL (self-audit request)
<ul>
<li>What it is: A standard HTTP GET request to your site’s own front page (<code>home_url()</code>), used to fetch and parse the public HTML so the plugin can detect Pixel installs, fired events, Advanced Matching, eventID dedupe, etc.</li>
<li>What data is sent: Only the HTTP GET itself. The User-Agent header is set to <code>ForegroundCAPIHealth/1.0 (+https://foreground.agency)</code> to identify the audit traffic in your access logs. No personal data, no admin identifiers, no cookies, no user IDs.</li>
<li>When: Only when a WordPress administrator manually clicks “Run audit on this site” inside Tools → Meta CAPI Health. There is no cron, no front-end trigger, and no automatic re-run.</li>
<li>Where: The request loops back to your own server (the same WordPress installation that has the plugin installed). It does not go to any external service.</li>
<li>Fallback chain: If HTTPS fails due to a local certificate issue, the request is retried once with <code>sslverify=false</code>, and as a last resort over <code>http://</code> to the same hostname. This is purely a local recovery path; no external host is ever contacted.</li>
</ul>
2. References to third-party services in the plugin’s UI (documentation only — no external call)
The plugin’s “How to fix” instructions name several third-party services so administrators know where to go in their existing accounts. The plugin does not connect to any of these. They are mentioned for instructional purposes only:
<ul>
<li>Meta / Facebook — <code>connect.facebook.net</code>, <code>graph.facebook.com</code>, Meta Events Manager, Meta Business Manager. Used as documentation references when explaining how to install a Meta Pixel, set up domain verification, or wire Conversions API. The plugin does not call any Meta endpoint. Meta’s terms: https://www.facebook.com/legal/terms — Meta’s privacy policy: https://www.facebook.com/privacy/policy</li>
<li>Third-party WordPress plugins mentioned by name in the fix steps (PixelYourSite, Meta for WordPress, CAPI Suite, Cookiebot, CookieYes, Complianz, Termly, Iubenda, OneTrust, GTM for WordPress). These are recommendations only. The plugin does not call, depend on, or communicate with any of them.</li>
<li>Foreground.agency — appears in the audit traffic User-Agent string for self-identification, and as the destination of an optional “Get the Pixel Fix” link shown in the admin UI only when an administrator clicks it. The plugin itself does not phone home to foreground.agency. Foreground privacy policy: https://foreground.agency/privacy</li>
</ul>
The “Fix it for me” CTA shown when an administrator’s score is below 85 is a plain HTML link that opens <code>https://foreground.agency/pixel-fix/?ref=wp-plugin</code> in a new tab. Nothing is transmitted unless the administrator chooses to click it.

Foreground CAPI Health Check

Audit your site's Meta Pixel + Conversions API setup. 12 checks against the 2026 iOS 17/18 stack. Free, no signup, no phone-home.

shan

Stop paying $30–150/month for a GTM Server Container. Send Conversions API events to Meta, Pinterest, and TikTok directly from your WordPress server. No premium tier, no SaaS subscription.
Three CAPI integrations in one install. Most plugins ship Meta only, or sell Pinterest and TikTok as paid add-ons. This one runs server-side dispatch to all three plus a bundled GTM template for GA4 + Google Ads (Enhanced Conversions, Conversion Linker, click-ID recovery for iOS Safari post-ITP). The same <code>event_id</code> flows browser-side and server-side so each platform deduplicates instead of double-counting.
Aggressive bot filtering, no false-positives on real customers. Layered detection (behavioral signals + ~9,500-CIDR datacenter list + AI-crawler classification for GPTBot / PerplexityBot / ClaudeBot / Google-Extended / Bytespider / etc.) blocks Lighthouse audits, scrapers, and ad-fraud bots. Multi-layered customer bypass — Apple iCloud Private Relay whitelist, ad-click ID recognition (<code>fbclid</code> / <code>gclid</code> / <code>ttclid</code>), logged-in customers, prior-visit <code>_fbp</code> / <code>_ga</code> cookies, Cloudflare Bot Management validation — keeps real shoppers visible. Purchase events are never blocked; pre-Purchase events held by the filter are replayed on eventual checkout so Meta sees the complete funnel.
<ul>
<li>Server-side CAPI to Meta, Pinterest, TikTok — every checkout & cart event, classic + block-based checkout, HPOS compatible. Per-platform retry isolates transient failures.</li>
<li>GTM template for browser-side tags — GA4 + Meta Pixel + Pinterest Tag + TikTok Pixel + Google Ads (Enhanced Conversions enabled, Conversion Linker auto-attached).</li>
<li>Event Log with By-IP view — paginated audit log, customer-protection badges prevent excluding real buyers, one-click exclude for confirmed bots, per-provider breakdown.</li>
<li>GDPR / CCPA modes — honors CMP opt-out signals, strict server-side consent strips PII when consent is denied (browser↔CAPI dedup still works on <code>event_id</code>).</li>
<li>Cache-safe — works with LiteSpeed, WP Rocket, Varnish, Cloudflare full-page cache. Click IDs captured into 1st-party cookies client-side; landing pages stay cacheable.</li>
<li>WP Dashboard widget — queue health at a glance: backlog, oldest pending, last successful dispatch, datacenter exclusions today.</li>
</ul>
If it helps your store, please <a href="https://wordpress.org/support/plugin/easy-meta-capi/reviews/#new-post" rel="ugc">leave a review</a> — it genuinely helps other merchants find this plugin.
<h3>External Services</h3>
This plugin connects your website to external services to send event data.
<ul>
<li>Service Used: Meta Conversion API (graph.facebook.com)
<ul>
<li>Purpose: To send user interaction and e-commerce event data from your server to Meta’s servers for ad performance measurement, optimization, and audience building.</li>
<li>Data Sent: Event details (product ID, price) and user parameters (IP address, user agent, hashed email/name/phone, Facebook cookies) are sent when a user performs a key action.</li>
</ul>
</li>
<li>Service Used: TikTok Events API (business-api.tiktok.com)
<ul>
<li>Purpose: Same as Meta CAPI, providing server-side conversion tracking for TikTok Ads optimization and attribution.</li>
<li>Data Sent: Event details (product ID, price, currency) and user parameters (IP address, user agent, hashed email/phone/external_id, ttp / ttclid cookies) are sent upon user action. Optional under the merchant’s TikTok credentials — the plugin only sends to TikTok if the credentials are configured.</li>
</ul>
</li>
<li>Service Used: Pinterest Conversions API (api.pinterest.com)
<ul>
<li>Purpose: Same as the Meta CAPI, providing reliable tracking for ad performance and audience building on Pinterest.</li>
<li>Data Sent: Event details and hashed user parameters are sent upon user action.</li>
</ul>
</li>
<li>Service Used: Google Tag Manager (googletagmanager.com)
<ul>
<li>Purpose: To load a JavaScript container from Google’s servers that allows you to manage and deploy marketing and analytics tags.</li>
<li>Data Sent: The plugin provides your GTM Container ID to Google to fetch the correct script. GTM itself may collect data based on how you configure your tags.</li>
</ul>
</li>
<li>Service Used: Cloud-provider IP range list — <code>raw.githubusercontent.com/rezmoss/cloud-provider-ip-addresses</code>
<ul>
<li>Purpose: Used by the optional Datacenter IP filter to keep the bot blocklist current. Daily background fetch downloads CIDR ranges for AWS, Google Cloud, Azure, Cloudflare, DigitalOcean, Linode, Vultr, Oracle Cloud, and Fastly so events from those ranges can be filtered out before reaching Meta / Pinterest / TikTok.</li>
<li>Data Sent: None. The plugin only downloads public IP-range manifests; no visitor data is sent to GitHub.</li>
<li>License: Source repository is CC0-licensed.</li>
</ul>
</li>
<li>Service Used: Apple iCloud Private Relay egress IP list — same <code>raw.githubusercontent.com/rezmoss/cloud-provider-ip-addresses</code> source (folder <code>apple_private_relay/</code>)
<ul>
<li>Purpose: Used by the optional Datacenter IP filter to whitelist real Apple visitors who exit through Apple’s relay infrastructure. Daily background fetch downloads the merged CIDR list so iOS Safari users on Private Relay aren’t mistaken for datacenter bots.</li>
<li>Data Sent: None. The plugin only downloads the public manifest; no visitor data is sent.</li>
</ul>
</li>
</ul>
Shared hosting note. Some restrictive shared hosts block outbound HTTPS by default. If event delivery silently fails after install, ask your host to whitelist the following domains for outgoing connections: <code>graph.facebook.com</code>, <code>business-api.tiktok.com</code>, <code>api.pinterest.com</code>, and <code>raw.githubusercontent.com</code> (only needed if you keep “Auto-fetched” enabled on the Blocked Traffic tab — covers both the datacenter blocklist and the Apple Private Relay whitelist).
<h3>Advanced Configuration</h3>
Setup details for Consent Mode v2, the strict server-side consent mode (GDPR PII gating), CMP auto-block compatibility, and the WooCommerce Subscriptions integration. None of these are required for a basic CAPI setup — turn them on as your store needs them.
<h3>Consent Mode v2 Setup (GDPR / EU Compliance)</h3>
If you serve EU visitors, GA4 and Meta browser tags don’t fire when consent is denied — typically losing 20–50% of measured event volume. Google Consent Mode v2 recovers this: when consent is denied, GA4 / Meta tags switch to cookieless pings (anonymous beacons carrying event name, value, currency, timestamp but no client identifier). Google’s ML models the conversions from these pings and shows them mixed with observed ones in your reports. A single CMP integration repairs both GA4 and Meta attribution because the Meta Pixel template reads the same consent signals.
How to enable. Popular CMP plugins (Cookiebot, CookieYes, Complianz, Iubenda, Termly, OneTrust) all have a native Consent Mode v2 toggle in their settings — find and enable it. The CMP then calls <code>gtag('consent', 'default', {denied})</code> before GTM loads and <code>gtag('consent', 'update', {granted})</code> after the visitor accepts.
The bundled GTM template includes a paused “Consent Defaults (Pre-CMP)” tag. Enable it only if your CMP doesn’t set <code>gtag('consent', 'default', ...)</code> on its own (rare with modern CMPs).
<h3>Strict server-side consent mode (PII gating for CAPI)</h3>
Consent Mode v2 only controls browser tags. Server-side CAPI fires from PHP, never sees <code>gtag('consent', ...)</code> signals — so it transmits hashed PII regardless of cookie-banner choice. Fine outside the EU; a GDPR concern inside it.
The Privacy & Consent (Server-side) section has a Strict server-side consent toggle (default OFF). When enabled and the visitor has denied marketing consent in your CMP, identifying PII (<code>em</code>, <code>ph</code>, <code>fn</code>, <code>ln</code>, address, <code>fbp</code>, <code>fbc</code> …) is stripped from the CAPI payload. The event still ships with <code>event_id</code>, <code>value</code>, <code>currency</code>, <code>contents</code> — Cookiebot, CookieYes, and Complianz cookies are read automatically; other CMPs supply state via the <code>mcapi_marketing_consent_granted</code> filter.
Why this matters alongside Consent Mode v2. Denied-consent browser pixels switch to cookieless pings — modeled, not observed. With Strict server-side consent ON, your server-side CAPI ships alongside that ping carrying the same <code>event_id</code>. Meta dedupes by <code>event_id</code> and now has an observed server signal feeding the same conversion record the cookieless ping created — cleaner Event Match Quality than browser-only or naïve “send everything” CAPI, and GDPR-defensible because no identifying data leaves your server.
Default OFF preserves match quality for existing non-EU setups. Recommended ON once Consent Mode v2 is configured in your CMP.
<h3>CMP Auto-Blocking and the Plugin’s Inline Scripts</h3>
CMPs with “auto-blocking” (Cookiebot, CookieYes, others) scan every <code><script></code> tag on load and convert anything they suspect of tracking to <code>type="text/plain"</code> until consent. The plugin’s inline scripts only POST first-party events to your own REST endpoint — but a generic auto-blocker can’t tell. To avoid a silent break, every plugin-rendered inline script ships with opt-out attributes for Cookiebot (<code>data-cookieconsent="ignore"</code>), CookieYes (<code>data-cookieyes="cookieyes-necessary"</code>), and Complianz (<code>data-cmplz-no-cookielaw="1"</code>). For other CMPs (OneTrust, Quantcast, in-house), append your own attribute via the <code>mcapi_inline_script_attrs</code> filter.
<h3>WooCommerce Subscriptions Integration</h3>
By default, every WooCommerce Subscriptions auto-renewal sends a fresh <code>Purchase</code> to Meta CAPI — credited to the original acquisition ad. Reported ROAS keeps climbing month after month from the same conversion, polluting optimization signals.
The plugin auto-detects WooCommerce Subscriptions and exposes:
Subscription Renewal Behavior (radio):
<ul>
<li>Default — renewals send as regular <code>Purchase</code>. Existing setups unchanged.</li>
<li>Skip — renewals not sent. Cleanest ROAS hygiene; you forfeit Meta’s LTV signal from renewals.</li>
<li>Tag — renewals still send <code>Purchase</code> but with <code>custom_data.customer_status = "subscription_renewal"</code> so you can filter them in Events Manager.</li>
<li>Subscribe / SubscriptionRenewal events — Meta’s standard <code>Subscribe</code> for sign-ups + a <code>SubscriptionRenewal</code> custom event for renewals. <code>Purchase</code> stays clean, advertisers using LTV-bidding can opt into both.</li>
</ul>
Tag every Purchase with customer_status (checkbox): adds <code>custom_data.customer_status</code> (<code>new_customer</code> / <code>returning_customer</code> / <code>subscription_renewal</code>) to every <code>Purchase</code> so Meta Advantage+ can bid acquisition vs. retention differently. Guest checkouts fall back to billing-email lookup.
<h3>Disclaimer</h3>
This plugin is an independent, community-driven implementation of server-side Conversions API protocols. It is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc., TikTok Ltd., Pinterest, Inc., Google LLC, Automattic Inc., or any other trademark holder referenced herein.
“Meta”, “Facebook”, and the Meta Pixel are trademarks of Meta Platforms, Inc. “TikTok” is a trademark of TikTok Ltd. “Pinterest” is a trademark of Pinterest, Inc. “Google Tag Manager”, “Google Ads”, and “GA4” are trademarks of Google LLC. “WooCommerce” is a trademark of Automattic Inc. All trademark references are used solely for descriptive interoperability purposes — to indicate which platforms this plugin can transmit data to under the merchant’s own configured credentials.
No user data is transmitted to any external service until the merchant explicitly configures their own platform credentials in the plugin settings. The plugin does not “phone home” or contact any developer-controlled server. The only outbound HTTP calls are: (1) merchant-configured CAPI endpoints, (2) the public CIDR manifests at raw.githubusercontent.com used by the optional Datacenter IP filter — no visitor data is sent in those manifest fetches.

CAPI Suite: Meta, Pinterest, TikTok, GTM

Free multi-platform server-side CAPI for Meta, Pinterest, TikTok + GTM dataLayer. Cache-safe, theme-agnostic, no cloud server needed.

Foreground CAPI Health Check vs CAPI Suite: Meta, Pinterest, TikTok, GTM