PixelFlow

Stop losing 30-50% of your WooCommerce conversions to iOS restrictions and ad blockers. PixelFlow is the no-code solution for implementing Meta’s Conversions API on WooCommerce – so your ads finally get the data they need to optimize.

• No more missing sales or conversions in Facebook ads manager
• See every single event and where it came from down to the campaign, adset and ad
• No for developers, Google Tags Manager or expensive solution

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:

• No developer needed — install plugin, click enable and you’re DONE.
• Unlimited event tracking — flat monthly pricing, no per-event fees or surprise charges
• Set up in minutes — not days or weeks

What You Get

• Recover lost conversions that browser-based tracking misses
• Improve Event Match Quality scores for better ad targeting and lower CPAs
• Track WooCommerce events automatically — Add to Cart, Checkout, Purchase
• Real-time event monitoring — see exactly what’s being sent to Meta
• 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.

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:

• Add to Cart — with product name, price, and quantity
• Initiate Checkout — captures cart totals
• Purchase — full order data including revenue

No manual setup. No custom code. Works instantly.

Additional options:

• Exclude free products from tracking
• Exclude admins and specific user roles
• Control which events fire and when

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 PixelFlow

Filters for Developers

pixelflow_external_id

From 1.1.18 the plugin derives external_id itself, as sha256(site_external_id . '_' . visitor_id) — the same value the PixelFlow browser script emits, so server-side and browser events resolve to one shopper. The visitor id is the only source: a WordPress user id, an email address, an order id or the Facebook cookie are never substituted for it, and an event with no visitor id is sent with no external_id at all.

This filter lets a site replace that value, suppress it, or supply one where the plugin resolved none. It runs on every event, including when nothing resolved. Returning an empty value or null omits the field.

add_filter( 'pixelflow_external_id', function ( $external_id, $context ) {
    // Supply an identifier where the plugin found none — the previous behaviour.
    if ( empty( $external_id ) && ! empty( $context['order'] ) ) {
        return hash( 'sha256', (string) $context['order']->get_billing_email() );
    }

    return $external_id;
}, 10, 2 );

The $context array is a public contract from 1.1.18 onward, but its keys are not uniform across event types — a callback must tolerate a missing key rather than assume one:

• AddToCart — product_id, variation_id, and bot_rule when the request was classified as an anonymous add-to-cart URL
• InitiateCheckout — no keys at all
• Purchase — order, plus the consent overrides consent, no_decision, source, and allow_live (false when the request is not the buyer’s, such as a payment-gateway callback or a status change made in wp-admin)
• A held event replayed after consent is granted — product_id and variation_id from the stored recipe

pixelflow_useragent_bot_patterns

The plugin does not send events for requests whose user agent matches a known automation signature. The list includes generic HTTP client libraries (guzzle, httpx, aiohttp), which a store’s own mobile app or partner integration may legitimately use. When an event is withheld this way, the site’s debug log names the matched signature, so a false positive can be identified and then removed here.

add_filter( 'pixelflow_useragent_bot_patterns', function ( $patterns ) {
    // Our own mobile app uses Guzzle; stop treating it as automation.
    return array_values( array_diff( $patterns, array( 'guzzle' ) ) );
} );

Each entry is matched as a case-insensitive substring of the user agent.

Privacy Policy

PixelFlow integrates with Meta’s Conversions API to track customer actions on your website (when configured). This may include:

• Page views
• Product interactions
• Purchase events
• Form submissions

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:
* PixelFlow Privacy Policy
* Meta Business Tools

Additional Information

Links:
* PixelFlow Website
* Documentation
* Event Classes Reference
* Support

Requirements:
* WordPress 6.5 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
* GitHub Repository – feel free to contribute or report issues