pixelflow

Stop losing 30-50% of your WooCommerce conversions to iOS restrictions and ad blockers. <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow</a> is the no-code solution for implementing Meta’s Conversions API on WooCommerce – so your ads finally get the data they need to optimize.
<ul>
<li>No more missing sales or conversions in Facebook ads manager</li>
<li>See every single event and where it came from down to the campaign, adset and ad</li>
<li>No for developers, Google Tags Manager or expensive solution</li>
</ul>
Why PixelFlow?
Most server-side tracking solutions are built for developers or enterprise teams. They require complex setups, expensive consultants, or per-event pricing that spirals out of control.
PixelFlow is different:
<ul>
<li>No developer needed — install plugin, click enable and you’re DONE.</li>
<li>Unlimited event tracking — flat monthly pricing, no per-event fees or surprise charges</li>
<li>Set up in minutes — not days or weeks</li>
</ul>
What You Get
<ul>
<li>Recover lost conversions that browser-based tracking misses</li>
<li>Improve Event Match Quality scores for better ad targeting and lower CPAs</li>
<li>Track WooCommerce events automatically — Add to Cart, Checkout, Purchase</li>
<li>Real-time event monitoring — see exactly what’s being sent to Meta</li>
<li>Works alongside your existing Pixel — CAPI supplements browser tracking, it doesn’t replace it. PixelFlow automatically loads both your pixel & CAPI for you for perfect event. deduplication and more coverage.</li>
</ul>
Why Server-Side Tracking Matters
Since iOS 14, Meta’s browser-based Pixel misses up to half your conversions. Ad blockers make it worse. When Meta doesn’t receive your conversion data, it can’t optimize your campaigns — so you pay more for worse results. 
PixelFlow sends events directly from your server to Meta, bypassing ad blockers and privacy restrictions entirely. Your ads get complete data. Your ROAS improves.
Built for WooCommerce
When WooCommerce is active, PixelFlow automatically tracks:
<ul>
<li>Add to Cart — with product name, price, and quantity</li>
<li>Initiate Checkout — captures cart totals</li>
<li>Purchase — full order data including revenue</li>
</ul>
No manual setup. No custom code. Works instantly.
Additional options:
<ul>
<li>Exclude free products from tracking</li>
<li>Exclude admins and specific user roles</li>
<li>Control which events fire and when</li>
</ul>
Not Using WooCommerce? We’ve Got You Covered. 
Running a WordPress site without an online store? PixelFlow works for you too without the need for a plugin. Learn more at <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow</a>
<h3>Privacy Policy</h3>
PixelFlow integrates with Meta’s Conversions API to track customer actions on your website (when configured). This may include:
<ul>
<li>Page views</li>
<li>Product interactions</li>
<li>Purchase events</li>
<li>Form submissions</li>
</ul>
All data is processed according to Meta’s privacy policies and your local privacy regulations. Please ensure you have appropriate user consent mechanisms in place if required by law (e.g., GDPR, CCPA).
For more information: 
* <a href="https://pixelflow.so/privacy" rel="nofollow ugc">PixelFlow Privacy Policy</a> 
* <a href="https://www.facebook.com/business/tools" rel="nofollow ugc">Meta Business Tools</a>
<h3>Additional Information</h3>
Links: 
* <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow Website</a> 
* <a href="https://docs.pixelflow.so" rel="nofollow ugc">Documentation</a> 
* <a href="https://docs.pixelflow.so/pixelflow-classes-document" rel="nofollow ugc">Event Classes Reference</a> 
* <a href="https://pixelflow.so/contact" rel="nofollow ugc">Support</a>
Requirements: 
* WordPress 5.0 or higher 
* PHP 7.4 or higher 
* WooCommerce 4.0+ (optional, for e-commerce features)
Developer Resources: 
* The plugin is developer-friendly with filters and hooks 
* Custom event tracking can be implemented using PixelFlow classes 
* Compatible with custom WooCommerce themes 
* <a href="https://github.com/PixelFlow-org/pixelflow-wordpress" rel="nofollow ugc">GitHub Repository</a> – feel free to contribute or report issues

PixelFlow

Facebook Conversions API for WooCommerce. One-click setup. Auto track WooCommerce events to Meta with 100% accuracy. Bypass iOS restrictions & ad  …

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.

PixelFlow vs Foreground CAPI Health Check