firepixel

FirePixel for WooCommerce connects your WooCommerce store to the <a href="https://firepixel.io" rel="nofollow ugc">FirePixel</a> platform, enabling server-side conversion tracking for Facebook/Meta Ads, TikTok Ads, and Google Ads.
Key Features:
<ul>
<li>Server-side event delivery via FirePixel API — helps reduce signal loss from ad blockers, browser restrictions, and iOS privacy changes</li>
<li>Automatic tracking of key WooCommerce events: AddToCart, RemoveFromCart, ViewCart, ViewContent, InitiateCheckout, Purchase, OrderStatusChanged, and more</li>
<li>Frontend pixel/tag script injection for supported ad platforms when configured</li>
<li>Event deduplication to help prevent double-counting</li>
<li>Background async event queue — no impact on page load time</li>
<li>Debug logging via the WooCommerce logger</li>
<li>Quick Connect flow for easy API key setup</li>
<li>Multi-platform ad tracking support for Meta/Facebook, TikTok, and Google Ads</li>
</ul>
Tracked Events:
<ul>
<li>AddToCart</li>
<li>RemoveFromCart</li>
<li>ViewCart</li>
<li>ViewContent (product pages)</li>
<li>InitiateCheckout</li>
<li>Purchase</li>
<li>OrderStatusChanged</li>
</ul>
<h3>External services</h3>
This plugin connects to external services to deliver server-side conversion tracking and to inject client-side pixel/tag scripts on your storefront. Below is a full disclosure of each service, what data is sent, and when.
<h4>FirePixel API (api.firepixel.io)</h4>
This is the core service this plugin is built around. When the plugin is enabled and a tracked WooCommerce event occurs, such as AddToCart, ViewContent, InitiateCheckout, Purchase, or OrderStatusChanged, it queues an event payload in the database and sends it asynchronously to the FirePixel API in the background via WooCommerce Action Scheduler. WP-Cron is used only if Action Scheduler is not available.
The payload may include the event name, product or order data such as IDs, names, prices, quantities, order totals, currency, and browser signals such as IP address, user agent, referrer, click IDs, cookies, and other attribution parameters used for accurate server-side conversion tracking.
FirePixel may use this data to forward server-side events to the ad platforms configured in your FirePixel dashboard, including Meta/Facebook Ads, TikTok Ads, and Google Ads.
No data is sent unless the plugin is explicitly enabled in settings and valid API credentials are configured.
<ul>
<li>Service provider: FirePixel</li>
<li>Terms of service: https://firepixel.io/terms/</li>
<li>Privacy policy: https://firepixel.io/privacy/</li>
</ul>
<h4>FirePixel App (app.firepixel.io)</h4>
Used only during the Quick Connect setup flow. When a store owner clicks “Quick Connect”, the plugin exchanges an access token with the FirePixel app to retrieve API credentials automatically. The store URL and access token are sent as part of this one-time handshake.
No conversion event data is sent to the FirePixel App during this setup flow, and no setup handshake data is sent after setup is complete.
<ul>
<li>Service provider: FirePixel</li>
<li>Terms of service: https://firepixel.io/terms/</li>
<li>Privacy policy: https://firepixel.io/privacy/</li>
</ul>
<h4>Meta/Facebook Pixel</h4>
If Meta/Facebook Pixel IDs are configured in your FirePixel account, the plugin may inject the Meta Pixel script into frontend pages of your store. This script is loaded in the visitor’s browser and may send browser-side page view and conversion signals to Meta/Facebook.
This only occurs when Meta/Facebook Pixel settings are present in your FirePixel configuration.
<ul>
<li>Service provider: Meta Platforms, Inc.</li>
<li>Terms of service: https://www.facebook.com/legal/terms</li>
<li>Privacy policy: https://www.facebook.com/privacy/policy/</li>
</ul>
<h4>TikTok Pixel</h4>
If TikTok Pixel IDs are configured in your FirePixel account, the plugin may inject the TikTok Pixel script into frontend pages of your store. This script is loaded in the visitor’s browser and may send browser-side page view and conversion signals to TikTok Ads.
This only occurs when TikTok Pixel settings are present in your FirePixel configuration.
<ul>
<li>Service provider: TikTok</li>
<li>Terms of service: https://www.tiktok.com/legal/page/row/terms-of-service/en</li>
<li>Privacy policy: https://www.tiktok.com/legal/page/row/privacy-policy/en</li>
</ul>
<h4>Google Tag Manager / Google Ads (googletagmanager.com)</h4>
If Google Ads or Google Tag IDs are configured in your FirePixel account, the plugin may inject the Google Tag script into frontend pages of your store. This script is loaded directly from Google’s servers in the visitor’s browser and may send page view and conversion data to Google Ads on your behalf.
This only occurs when Google Ads or Google Tag IDs are present in your FirePixel configuration.
<ul>
<li>Service provider: Google LLC</li>
<li>Terms of service: https://policies.google.com/terms</li>
<li>Privacy policy: https://policies.google.com/privacy</li>
</ul>
<h4>Ad platform forwarding</h4>
FirePixel forwards the server-side events it receives to whichever ad platforms you have configured in your FirePixel dashboard, including Meta/Facebook Ads, TikTok Ads, and Google Ads.
The plugin itself sends tracked event data only to FirePixel. FirePixel’s own terms of service and privacy policy govern any onward transmission to third-party ad platforms.
<ul>
<li>FirePixel Terms of service: https://firepixel.io/terms/</li>
<li>FirePixel Privacy policy: https://firepixel.io/privacy/</li>
</ul>

FirePixel for WooCommerce

Server-side WooCommerce conversion tracking for Meta, TikTok, and Google Ads via the FirePixel platform.

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.

FirePixel for WooCommerce vs Foreground CAPI Health Check