Title: CapiFlow – Conversions API (CAPI) Tracking for WooCommerce Author: capiflow Published: 11. meje 2026 Last modified: 28. julija 2026 --- Tykače pytać ![](https://ps.w.org/capiflow/assets/banner-772x250.png?rev=3529278) ![](https://ps.w.org/capiflow/assets/icon-256x256.png?rev=3529278) # CapiFlow – Conversions API (CAPI) Tracking for WooCommerce Wot [capiflow](https://profiles.wordpress.org/capiflow/) [Sćahnyć](https://downloads.wordpress.org/plugin/capiflow.1.0.2.zip) * [Podrobnosće](https://hsb.wordpress.org/plugins/capiflow/#description) * [Pohódnoćenja](https://hsb.wordpress.org/plugins/capiflow/#reviews) * [Instalacija](https://hsb.wordpress.org/plugins/capiflow/#installation) * [Wuwiće](https://hsb.wordpress.org/plugins/capiflow/#developers) [Podpěra](https://wordpress.org/support/plugin/capiflow/) ## Wopisanje **CapiFlow** sends supported WooCommerce events from your server to Meta’s Conversions API (CAPI) — helping reduce the impact of browser-side tracking limitations like ad blockers, Safari ITP, and Firefox ETP. #### Why Server-Side Tracking Matters When the Meta pixel is blocked, event data may not reach Meta — affecting ad optimization. CapiFlow complements the browser pixel by sending events server-side with a matching` event_id` for deduplication. #### How It Works 1. **Install & Activate** — Setup wizard launches automatically 2. **Enter Pixel ID + Access Token** — From Meta Events Manager 3. **Click Test Connection** — Events start flowing No theme edits. No GTM server container required. No separate server-container subscription needed for the built-in Meta CAPI workflow. #### Core Features **Server-Side Event Tracking** * 🎯 **7 Standard Events** — Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, PageView * 🔄 **Deduplication** — Browser pixel and server events share the same `event_id` to support Meta’s deduplication * 🛡️ **First-Party Event Endpoint** — Browser events can be delivered through your own domain where configured * 🔐 **SHA-256 PII Hashing** — Email, phone, name hashed before leaving your server **Event Match Quality Support** — `fbc`, `fbp`, `external_id`, client IP, user agent, and hashed customer data (email, phone, name) for logged-in users. **Analytics & Monitoring** * 📈 Dashboard — event breakdown and source attribution * 🔍 Debug console — payloads and Meta API responses * 🏥 System health — token, queue, connection test * 🛒 Cart monitor — abandoned cart summary **Data Quality & Control** * 📞 Phone validation at checkout * 🔒 COD Purchase gate — hold events until admin confirms * 📋 Order metabox and columns — per-order CAPI status **Developer Tools** * 🔧 Code injection — GTM, analytics, chat widgets (admin-only) * 🪝 Filter hooks — `capiflow_proxy_url`, `capiflow_has_tracking_consent` * 📦 HPOS compatible — WooCommerce High-Performance Order Storage support * ⏱️ Action Scheduler queue — async event delivery with retry logic #### CapiFlow Pro CapiFlow Pro is a separate addon that extends the free plugin with: * Phone reputation scoring and fraud detection * Negative Purchase events for cancelled/refunded orders * Multi-pixel and category-based pixel routing * COD auto-confirm with courier integration * Real-time EMQ score display from Meta API * Blacklist management for known fraud patterns * Advanced order quality tools Learn more on the [CapiFlow website](https://capiflowpro.com). #### Compatibility * **Gateways:** bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard WooCommerce gateways * **Themes:** Any theme — Classic, Block (FSE), page builders * **WooCommerce:** HPOS and legacy post-based orders * **Consent:** CookieYes, Complianz, CookieBot, GDPR Cookie Consent, custom filter hook #### Requirements * WordPress 6.0+ * WooCommerce 7.0+ * PHP 7.4+ * OpenSSL PHP extension * Meta Pixel ID and System User Access Token #### External Services This plugin connects to the following third-party services: **Meta (Facebook) Conversions API** CapiFlow sends WooCommerce event data to the Meta Conversions API via: `https:// graph.facebook.com/` This connection is made from your server to Meta’s servers when a configured tracking event occurs. No data is sent until a valid Pixel ID and Access Token are configured. Data transmitted includes: * Hashed email, phone, first and last name (SHA-256) * Client IP address and Browser User Agent * Meta Click ID (_fbc) and Browser ID (_fbp) cookies * Order total, currency, and event metadata All personal data is SHA-256 hashed before transmission. * [Meta Terms of Service](https://www.facebook.com/terms.php) * [Meta Privacy Policy](https://www.facebook.com/privacy/policy/) * [Meta Platform Terms](https://developers.facebook.com/terms/) **Meta Pixel JavaScript SDK** This plugin loads the Meta Pixel SDK from: `https://connect.facebook.net/en_US/fbevents. js` Loaded on frontend pages when a Pixel ID is configured. The SDK is hosted by Meta. * [Meta Terms of Service](https://www.facebook.com/terms.php) * [Meta Privacy Policy](https://www.facebook.com/privacy/policy/) #### Privacy For server-side events, all personal data is SHA-256 hashed before transmission. For browser events, the Meta Pixel SDK handles hashing via Advanced Matching. This plugin does not store raw PII in its own tables. See [Meta’s privacy policy](https://www.facebook.com/privacy/policy/). #### Cookies * `cs_uid` — Random visitor identifier for `external_id` deduplication. 180 days. No PII. * `_fbc` — Meta Click ID. Set by Meta SDK on ad click. CapiFlow reads/extends server- side. 180 days. * `_fbp` — Meta Browser ID. Set by Meta SDK. CapiFlow reads/extends server-side. 180 days. All cookies are first-party and contain no personally identifiable information. #### Data Storage * `{prefix}_capiflow_events` — Queued/sent event payloads. Auto-purged after delivery. * `{prefix}_capiflow_analytics` — Daily aggregated analytics. Auto-purged by retention settings. * Order metadata with `_capiflow_` prefix. Removed on uninstall if „Keep Data“ is disabled. * Logs in `wp-content/uploads/capiflow-logs/` with `.htaccess` protection. Auto- cleaned daily. #### Consent By default, events fire once configured. Enable „Consent Enforcement“ in Settings to respect CMP signals for both browser and server events. Supported CMPs: CookieYes, Complianz, CookieBot, GDPR Cookie Consent. Custom integration via `capiflow_has_tracking_consent` filter. When Consent Enforcement is enabled, browser and server-side events are blocked until valid tracking consent is detected. Store owners are responsible for lawful consent configuration where required by privacy regulations. ## Fota wobrazowki [⌊Setup Wizard — Guided first-time configuration⌉⌊Setup Wizard — Guided first-time configuration⌉[ **Setup Wizard** — Guided first-time configuration [⌊Settings Page — Pixel ID, Access Token, and connection test⌉⌊Settings Page — Pixel ID, Access Token, and connection test⌉[ **Settings Page** — Pixel ID, Access Token, and connection test [⌊Analytics Dashboard — Event tracking overview⌉⌊Analytics Dashboard — Event tracking overview⌉[ **Analytics Dashboard** — Event tracking overview [⌊Event Configuration — Per-event browser and server toggles⌉⌊Event Configuration— Per-event browser and server toggles⌉[ **Event Configuration** — Per-event browser and server toggles [⌊System Health — Token validity and queue status⌉⌊System Health — Token validity and queue status⌉[ **System Health** — Token validity and queue status [⌊Debug Console — Event log with API responses⌉⌊Debug Console — Event log with API responses⌉[ **Debug Console** — Event log with API responses [⌊Order Columns — CAPI sync status in order list⌉⌊Order Columns — CAPI sync status in order list⌉[ **Order Columns** — CAPI sync status in order list [⌊Pixel Helper — Browser and server event verification⌉⌊Pixel Helper — Browser and server event verification⌉[ **Pixel Helper** — Browser and server event verification [⌊Event Test Tool — All events delivery status⌉⌊Event Test Tool — All events delivery status⌉[ **Event Test Tool** — All events delivery status [⌊Purchase Event — Server-side Purchase with API response⌉⌊Purchase Event — Server- side Purchase with API response⌉[ **Purchase Event** — Server-side Purchase with API response ## Instalacija 1. Install from WordPress plugins screen or upload `capiflow` to `/wp-content/plugins/`. 2. Activate through the **Plugins** menu. 3. Setup wizard launches — enter **Pixel ID** and **Access Token**. 4. Click **Test Connection** — check **CapiFlow Dashboard** to monitor. #### Getting an Access Token 1. [Meta Events Manager](https://www.facebook.com/events_manager2/) Select Pixel Settings Conversions API 2. Click **Generate Access Token** or create a System User 3. Paste into CapiFlow Settings Pixel Settings ## HSP ### Does this replace the Meta browser pixel? No. CapiFlow works alongside the browser pixel using Meta’s recommended redundant setup — both share a matching `event_id` for deduplication. ### Will this cause duplicate events? No. Matching `event_id` values ensure Meta deduplicates browser and server events automatically. ### Do I need a GTM server container or a service like Stape.io? No. CapiFlow sends events directly from your WooCommerce server to Meta — no separate GTM server container, third-party service, or monthly subscription needed. ### How does this support Event Match Quality? CapiFlow sends `fbc`, `fbp`, `external_id`, client IP, user agent, and hashed customer data — additional signals that can improve event matching vs browser-only tracking. ### How is privacy handled? All PII is SHA-256 hashed before transmission. Consent Enforcement toggle blocks events until CMP consent is granted. Privacy policy content auto-added to your WordPress Privacy Policy page. ### Which order storage is supported? Both traditional posts-based and HPOS (High-Performance Order Storage). Auto-detected, no configuration needed. ### Does this work with my payment gateway? Yes. CapiFlow uses WooCommerce’s standard order status hooks. Compatible with bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard gateways. ### What happens with COD orders? Purchase event is held until admin confirms the order, preventing unverified COD orders from reaching Meta. ### Do I need Google Tag Manager? No. CapiFlow works standalone. If you need GTM or other scripts, a built-in code injection feature is included. ### What is CapiFlow Pro? A separate addon that adds fraud protection, negative Purchase events for cancellations, multi-pixel routing, courier integration, and real-time EMQ scores. [Learn more](https://capiflowpro.com). ## Pohódnoćenja ![](https://secure.gravatar.com/avatar/91c26dce9549d7d1726d81bec9a97ee2c88e7a1538db552caf03b9288a072cc2? s=60&d=retro&r=g) ### 󠀁[Underrated plugin for Meta’s ad optimization systems](https://wordpress.org/support/topic/underrated-plugin-for-metas-ad-optimization-systems/)󠁿 [tictubso](https://profiles.wordpress.org/tictubso/) 29. julija 2026 This is a genuinely good and useful plugin. It helped me bridge the gap between my WooCommerce site and Meta’s Conversions API system, to help get cleaner data allowing us to optimize Instagram and Facebook ads. The support from CapiFlow is top-notch, this plugin deserves a lot more attention than it’s getting. 5 stars from me every day of the week. ![](https://secure.gravatar.com/avatar/9c049bd6b3b30d313f168638dd3b87a4310e650e8bd5ccc1269dee2de2cae1e8? s=60&d=retro&r=g) ### 󠀁[I found this addon by chance but it’s great](https://wordpress.org/support/topic/i-found-this-addon-by-chance-but-its-great/)󠁿 [waleedgaafar](https://profiles.wordpress.org/waleedgaafar/) 15. junija 2026 1 reply I found this addon by chance but it’s great and very useful for me I used it in all my websites [ Čitajće 2 pohódnoćeni ](https://wordpress.org/support/plugin/capiflow/reviews/) ## Sobuskutkowarjo a wuwiwarjo „CapiFlow – Conversions API (CAPI) Tracking for WooCommerce“ je softwara wotewrjeneho žórła. Slědowacy ludźo su k tutomu tykačej přinošowali. Sobuskutkowarjo * [ capiflow ](https://profiles.wordpress.org/capiflow/) [Přełožće „CapiFlow – Conversions API (CAPI) Tracking for WooCommerce“ do swojeje rěče.](https://translate.wordpress.org/projects/wp-plugins/capiflow) ### Na wuwiću zajimowany? [Přehladajće kod](https://plugins.trac.wordpress.org/browser/capiflow/), hladajće do [SVN-repozitorija](https://plugins.svn.wordpress.org/capiflow/) abo abonujće [wuwiwanski protokol](https://plugins.trac.wordpress.org/log/capiflow/) přez [RSS](https://plugins.trac.wordpress.org/log/capiflow/?limit=100&mode=stop_on_copy&format=rss). ## Protokol změnow #### 1.0.2 — 2026-07-29 * Fix: Prevent firing Purchase events for pre-existing orders created prior to CapiFlow installation or >7 days ago when order status is changed in WP Admin/ background. * Fix: Add self-healing installation timestamp and multi-layered pre-installation protection guard to prevent invalid server-side Purchase attribution. #### 1.0.1 — 2026-05-22 * Update WordPress compatibility header to Tested up to 7.0 for WordPress 7.0 „ Armstrong“ release. #### 1.0.0 — 2026-05-01 * Initial public release * Server-side tracking for 7 Meta standard events via Conversions API * Browser + server event deduplication with matching event_id * First-party event endpoint, SHA-256 PII hashing, Advanced Matching * COD Purchase gate, phone validation, analytics dashboard * Debug console, system health, setup wizard * HPOS compatible, Action Scheduler queue, CMP integration ## Meta * Version **1.0.2** * Last updated **1 tydźeń** * Active installations **Mjenje hač 10** * WordPress version ** 6.0 abo nowši ** * Tested up to **7.0.2** * PHP version ** 7.4 abo nowši ** * Language * [English (US)](https://wordpress.org/plugins/capiflow/) * Tags * [Conversions API](https://hsb.wordpress.org/plugins/tags/conversions-api/)[Facebook Pixel](https://hsb.wordpress.org/plugins/tags/facebook-pixel/) [Meta Pixel](https://hsb.wordpress.org/plugins/tags/meta-pixel/)[Server Side Tracking](https://hsb.wordpress.org/plugins/tags/server-side-tracking/) [woocommerce](https://hsb.wordpress.org/plugins/tags/woocommerce/) * [Rozšěrjeny napohlad](https://hsb.wordpress.org/plugins/capiflow/advanced/) ## Pohódnoćenja 5 out of 5 stars. * [ 2 5-star reviews ](https://wordpress.org/support/plugin/capiflow/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/capiflow/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/capiflow/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/capiflow/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/capiflow/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/capiflow/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/capiflow/reviews/) ## Sobuskutkowarjo * [ capiflow ](https://profiles.wordpress.org/capiflow/) ## Podpěra Rozrisane problemy zańdźeneju dweju měsacow: 0 z 1 [Forum pomocy pokazać](https://wordpress.org/support/plugin/capiflow/)